CHATBOTS

Intercom Warehouse-Receipt Refund Release

When a warehouse confirms a returned item has arrived, this workflow captures the held Stripe refund, closes the RMA.

CategoryChatbots
Enginesim
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWarehouse-receipt webhook receivedHTTP webhook
  • ActionMatch and validate open RMA by tracking number in PostgresPostgreSQLPostgres
  • LogicCompute final refund amount with fee rules
  • ActionCapture the held Stripe refundStripeStripe
  • ActionMark RMA completed with refund id in PostgresPostgreSQLPostgres
  • OutputConfirm refund amount and timing in IntercomIntercomIntercom

What it does

Closes out the return at the moment the item lands in the warehouse. A receipt webhook releases the previously staged Stripe refund, updates the RMA to completed, and sends the customer a confirmation in Intercom so they know exactly when and how much they are getting back.

When to use it

Use it when refunds are issued only after physical inspection but the release step is manual and slow. This ties the refund directly to the receipt event so customers are paid the day their return arrives.

How it works

  1. 1A warehouse-receipt webhook fires when the returned package is scanned in.
  2. 2The RMA is matched in Postgres by tracking number and validated as still open and within authorization.
  3. 3A logic step checks for a restocking fee or partial-refund rule and computes the final amount.
  4. 4The held Stripe refund is captured at the computed amount.
  5. 5The RMA record is marked completed with the refund id and date.
  6. 6An Intercom message confirms the refund amount and expected settlement window to the customer.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect StripeCustomers, subscriptions, payments.
  4. 4
    Connect IntercomConversations, contacts, articles.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.