CHATBOTS

Intercom RMA Label Issuance and Refund

Once a return is approved in Intercom, this workflow generates a prepaid return label, emails it to the customer via Gmail.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerIntercom conversation marked RMA approvedIntercomIntercom
  • ActionWrite RMA record with reason and expiry to PostgresPostgreSQLPostgres
  • ActionGenerate prepaid return label and store tracking numberPostgreSQLPostgres
  • ActionEmail label and return instructions to customerGmailGmail
  • ActionStage held Stripe refund keyed to the RMAStripeStripe
  • OutputPost tracking number and confirmation to IntercomIntercomIntercom

What it does

Handles the post-approval mechanics of a return. After an agent or bot marks an Intercom conversation as approved, it creates the RMA record, issues a prepaid shipping label, sends that label to the customer, and stages the Stripe refund so it releases the moment the warehouse scans the package in.

When to use it

Use it when your team approves returns quickly but the label-and-refund busywork still eats agent time and creates inconsistent customer follow-up. This makes the whole back half of the return hands-off.

How it works

  1. 1An Intercom conversation moves to an "RMA approved" state, triggering the flow.
  2. 2A new RMA row is written to Postgres with the order id, reason, and an expiry date.
  3. 3A prepaid return label is generated and stored, and its tracking number is saved to the RMA record.
  4. 4The label and return instructions are emailed to the customer through Gmail.
  5. 5A Stripe refund is created in a held/pending state keyed to the RMA so it settles on package receipt.
  6. 6Intercom is updated with the tracking number and a confirmation note closing the loop.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect IntercomConversations, contacts, articles.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Connect StripeCustomers, subscriptions, payments.
  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.