How we handle GDPR data-subject requests on a deadline
Legal
The vendor-onboarding agent we run on Kortix — connected to Gmail, Google Sheets, and Slack. Every day it checks new vendor requests for a completed W-9, banking form, and signed contract, records each vendor's status to our vendor register, and flags anything missing or invalid — never approving a vendor or touching payment setup itself.
A new vendor shows up as an email thread: a name, a contact, and — if we're lucky — three attachments. A W-9, a banking form, and a signed contract. Each one needs to be there, complete, and consistent with the others before the vendor is ready to be set up. Done by hand, that check gets skipped under deadline pressure, and the gap that slips through is exactly the one that matters: a vendor entered into a payment system on an unsigned contract or a W-9 with no TIN.
We run a vendor-onboarding agent on Kortix that checks the inbox every day, validates the required documents for every new vendor request against a fixed checklist, records the result to our vendor register, and flags anything missing or invalid in Slack. It collects, validates, and records; it never approves a vendor and never touches payment or banking setup.
Vendor onboarding paperwork is simple in principle and inconsistent in practice. A W-9 arrives unsigned. A banking form is missing the routing number. A contract comes back with the wrong entity name because someone copy-pasted from a template. None of these are hard to catch individually, but catching all three, for every vendor, every time, is the kind of checklist work that a busy person does thoroughly on the first vendor of the week and loosely on the tenth.
The cost of skipping it isn't visible until later — a vendor gets set up for payment on paperwork that turns out to be incomplete, and untangling it after the fact costs far more than the two minutes the check would have taken. What's missing isn't judgment about whether to onboard a vendor; it's someone reading every attachment against the same checklist, every time, without skipping ahead to the next request.
On Kortix, a daily cron re-prompts a fresh session with no memory of the prior run — the vendor register in Google Sheets is the record it works from. Each run reads new vendor-request threads from a Gmail label, checks each attachment against a fixed checklist (a complete, signed W-9; a complete banking form; a signed contract with a matching entity name), records the result for every vendor whether clean or flagged, drafts a follow-up email for anything missing or invalid, and posts a summary to Slack for a person to act on. It never marks a vendor approved and never sets up a payment method or banking profile.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the intake skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a vendor onboarding intake agent in this workspace.
Create the agent agents/vendor-onboarding.md. Its job is to check new vendor paperwork and record its status. It may use the Gmail and Google Sheets connectors and post to Slack.
Create the skill skills/vendor-doc-intake/SKILL.md with these rules:
Add a cron trigger vendor-intake to kortix.yaml. It runs the vendor-onboarding agent every day at 07:00 with the prompt "Load the vendor-doc-intake skill and process every new request in the Vendor Onboarding label."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect the inbox where vendor requests arrive, the register sheet and Slack. Credentials are brokered server-side and never enter the agent's machine.

Reads each new vendor request and its attachments.

Confirms the signed contract when it lives there.

Posts the daily batch of vendor statuses and flags.
Merge the change request, then start a session with the vendor-onboarding agent and send this prompt. Check the register rows and the drafted follow-ups before you let the schedule take over.
Process the new vendor requests in the Vendor Onboarding label in Gmail.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 07:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: vendor-intake name: Vendor document intake on: cron: "0 0 7 * * *" run: agent: vendor-onboarding prompt: Load the vendor-doc-intake skill and process every new request in the Vendor Onboarding label.The agent collects, checks and records. It never marks a vendor approved and never sets up a payment method, ACH enrollment or banking profile, even when all three documents are clean. Every follow-up email is a draft that a person reviews and sends.
Each run ends with one message in #finance. This is what a run looks like in the session:
Processed 5 new vendor requests. 3 are clean and 2 are flagged: one unsigned W-9 and one contract with a different legal name. Both follow-ups are drafted and waiting to be sent.
Once it works, paste any of these into the same session.
Each Monday, post to #finance the flagged vendors whose follow-up is more than 5 days old with no reply.
Also check each vendor for a current certificate of insurance, and flag it as missing or expired like the other documents.
Every Friday, post to #finance how many vendors arrived, how many were flagged and how many still wait for documents.
The agent handles vendor paperwork end to end except the decision that matters, so its access is scoped and its authority is capped below approval:
Vendor paperwork that used to get a thorough read on the first request and a quick skim by the tenth now gets the same checklist every time, recorded in one register instead of scattered across a dozen email threads. The agent collects, validates, and records; a person still decides who gets approved and who gets paid.