Integrations

Connecting Exchange It to Zapier

Updated Oct 9, 2026

Exchange It can send return activity to Zapier so you can automate downstream workflows across thousands of apps. Use this when you want events like a return being requested, approved, or resolved to kick off a Zap.

Where to find it

Go to the Integrations page and open the Zapier tab to find the Zapier Integration card. The Exchange It Zapier app is a private app, available by invite — the card includes a link to install it, and you can reach out to support if you run into issues.

Set it up

  1. In the Zapier Integration card, generate an API key. The key is created for your store and shown in full once. A banner reminds you this is the only time you will see the full key, so copy it immediately — use the Copy button next to the key field to put it on your clipboard.
  2. After you copy it, Exchange It stores only the last four digits for display; the card shows the key masked as •••••••• followed by those last four characters.
  3. Use the install link in the card to add the Exchange It Zapier app, then paste the API key into your Zapier connection settings when prompted.

Connect it in Zapier

The Exchange It Zapier integration is a private app available by invite. Use the link in the card to install the Exchange It Zapier app, then paste the API key you generated into your Zapier connection settings. If you run into any issues during setup, contact the Exchange It support team.

What each trigger sends

The following triggers are available: Return Requested, Approved, Declined, Inspected, Resolved, and Cancelled. Sample payloads are available in Zapier when you configure your Zap.

Each trigger delivers a payload describing the return. Key top-level fields include exchange_it_return_id, status, source, requested_at, approved_at, cancelled_at, order_name, customer_email, customer_name, has_exchange_request, exchange_method, refund_method, return_note, restocking_fee_applied, restocking_fee_amount, shipping_method, shipping_label_url, store_credit_amount, store_credit_currency, and resolved_externally.

The payload also includes nested data:

  • products — per-item detail such as product_title, variant_title, sku, quantity_returned, return_reason, requested_resolution, approval_status, exchange_method, exchange_variant_title, items_received, items_refunded, and restock_location.
  • refund_summary — amounts for discounts, taxes, shipping, and return fees, including total_discounts_amount, total_tax_amount, shipping_amount, return_fee_amount, and return_fee_percentage.
  • exchange_details — the exchange target with variant_id, variant_title, quantity, price, and image_url.

Managing and revoking

Once a key exists, the card shows it masked with two actions:

  • Regenerate Key issues a new API key and shows it once in full. The previous key stops working, so update your Zapier connection with the new key.
  • Revoke API Key deletes the stored key and clears its last-four reference, disconnecting Zapier until you generate a new one.

Because a regenerated key replaces the old one, treat regeneration as a rotation: copy the new key right away and paste it into Zapier.

Related articles