AI AGENTS
Provision Vendor Portal Access on Approval
When a vendor is marked approved in Notion, the flow creates their portal account, sets role-based permissions, and emails secure first-login credentials.
How it runs
The automated pipeline, trigger to output.
- TriggerVendor status set to Approved in NotionNotion
- LogicMap vendor category to least-privilege role
- ActionCreate portal account via provisioning endpointHTTP webhook
- ActionEmail secure first-login credentialsGmail
- OutputAppend access grant to Postgres audit logPostgres
What it does
Grants a newly approved vendor the access they need without IT touching a console. It provisions a portal account, assigns the correct role based on vendor category, sends first-login instructions, and records the access grant for compliance.
When to use it
When vendor approval and access provisioning are separate manual steps that cause delays, and you want least-privilege access granted the moment Finance signs off.
How it works
- 1A vendor record's status changing to "Approved" in Notion fires the trigger.
- 2A logic step maps the vendor category to a permission role (supplier, contractor, or service partner).
- 3The flow creates the portal account via an internal provisioning endpoint with that role.
- 4Gmail sends secure first-login credentials and a setup guide to the vendor contact.
- 5The grant is appended to a Postgres audit table for later review.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect GmailRead, draft, send, label.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.