AI AGENTS
Vendor Bank Detail Verification with Stripe Micro-Deposits
Collects a vendor's bank account, initiates Stripe micro-deposit verification, confirms ownership, and only marks the vendor payable once the deposits are matched.
How it runs
The automated pipeline, trigger to output.
- TriggerVendor submits bank details via webhookHTTP webhook
- ActionRegister account and start Stripe micro-depositsStripe
- LogicAwait deposit-amount confirmation; remind after 3 days
- ActionSend micro-deposit reminder email if unconfirmedGmail
- ActionVerify account with Stripe on correct matchStripe
- OutputPost payable-status confirmation to Finance SlackSlack
What it does
Verifies that the bank account a vendor submitted is real and owned by them before any money moves. It registers the account with Stripe, triggers micro-deposits, waits for the vendor to confirm the amounts, and updates payment status accordingly.
When to use it
When you need fraud-resistant proof of bank ownership before enabling ACH payouts, and you want the back-and-forth of micro-deposit confirmation managed automatically.
How it works
- 1A submitted bank-detail form hits the webhook trigger.
- 2The flow creates a Stripe connected bank account and starts micro-deposit verification.
- 3A logic branch waits for the vendor to enter the two deposit amounts; a reminder email goes out via Gmail if no response in 3 days.
- 4On a correct match, Stripe confirms the account.
- 5The vendor record is updated to "Payable" and a confirmation summary is posted to the Finance Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect GmailRead, draft, send, label.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.