FINANCE

Pay approved reimbursements via Stripe

When a reviewer approves a reimbursement in Slack, this verifies the employee's payout details and issues the Stripe transfer.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerReviewer approves reimbursement in SlackSlack
  • ActionLook up employee Stripe payout accountStripeStripe
  • LogicConfirm payout details and amount are valid
  • ActionIssue Stripe transfer for approved amountStripeStripe
  • OutputLog payout and confirm to employeeGoogle DriveGoogle Drive

What it does

Turns a Slack approval into an actual reimbursement payout. When a finance reviewer clicks approve on a pending expense, the flow confirms the employee's saved Stripe Connect account, issues the transfer for the approved amount, and records the payout reference. The employee gets a confirmation message with the amount and expected arrival date.

When to use it

Use this once expenses are already reviewed and you want approval to trigger payment without anyone logging into the Stripe dashboard. It closes the loop between decision and money movement and keeps an auditable payout log.

How it works

  1. 1A reviewer approves a reimbursement via a Slack interaction, which fires the trigger.
  2. 2The flow looks up the employee's Stripe Connect account and validates the approved amount is within the request.
  3. 3Branch logic confirms payout details exist; if missing, it routes back to the reviewer instead of paying.
  4. 4A Stripe transfer is created for the reimbursement amount.
  5. 5The payout reference is written to the records sheet and a confirmation is sent to the employee in Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect StripeCustomers, subscriptions, payments.
  3. 3
    Connect Google DriveDocs, sheets, slides, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.