> ## Documentation Index
> Fetch the complete documentation index at: https://docs.newie.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Newie + Zapier

> Connect Newie to Zapier, choose the right trigger event, and send Newie activity to another app.

Connect a Newie purchase or payment event to an action in another app, such as inviting a coaching client or recording an invoice. In Zapier, choose Newie as the **trigger** app and the other app as the **action** app.

You'll need a Zapier account and a plan with the other app that supports the action you want. Workflows using [Filter by Zapier](https://help.zapier.com/hc/en-us/articles/8496276332557-Add-conditions-to-Zap-workflows-with-filters) require a paid Zapier plan.

<span id="before-you-start" />

## Connect Newie to Zapier

1. In Newie, open **Settings → Integrations → Connect Zapier**. On Mac, open the **Integrations** tab in Settings. If the option says **Zapier Connected**, open that instead.
2. Choose **Set Up** if prompted. The **API Token** appears on this Newie screen; copy it.
3. In [Zapier](https://zapier.com), create a Zap and choose **Newie** as the trigger app.
4. Paste the token when Zapier asks you to connect your Newie account.

If an older version of Newie sends you to a Zapier invite page, accepting the invite alone does not supply the token. Return to Newie to copy it. If you still only see the invite, [update Newie](/guides/account-settings#check-your-version-and-update-newie) and reopen **Connect Zapier**. If the token does not load, contact Newie support with the error and your app version.

If the Zapier option is missing entirely, complete the account and payout setup steps shown in Settings.

## Choose when the workflow begins

For onboarding, the key decision is whether to act at purchase, at the billing start date or after payment is confirmed:

* **Subscription Created** can prepare the customer before a future start date.
* **Subscription Started** begins the workflow on the billing start date.
* **Payment Paid** waits for confirmation, including bank-debit payments.
* **One-Off Purchase Complete** runs when a one-off purchase becomes Active after payment succeeds. For BECS, it waits while the payment is processing.

A BECS Direct Debit subscription can become active while its payment is processing. Bank confirmation usually takes up to three business days, so use **Payment Paid** when access or fulfilment depends on confirmed payment.

Payment Paid can also confirm a separately collected **Setup Fee**, before the first regular subscription payment. If access must wait for that regular payment, have someone check the invoice in Newie before granting it. The trigger does not provide a Setup Fee flag for a filter to make that distinction.

## Build and test the action

Choose the other app and its action. In each action field, select the corresponding value from the Newie trigger sample—for example, select the customer's email for the action's recipient field. This is called mapping. Follow the [guide for that app](/integrations#integration-guides) for its required fields and account settings.

If the workflow is for one service, add an Offering ID filter as described below. **Payment Paid** also runs for renewals, instalments and separately collected Setup Fees, so a service filter alone does not make the action a one-time event.

### Prevent repeat invitations and tasks

For a client profile, search the connected app for the customer's email before creating another profile. For an invitation or task that should run once per purchase, check the purchase rather than the email: a returning customer can buy the same service again.

Use `subscriptionID` for a subscription or instalment plan, or `purchaseID` for a one-off purchase. If the app cannot search for that ID, keep an action log in [Google Sheets](/integrations/newie-google-sheets) or another searchable tool.

1. Before the invitation or task action, look up the purchase ID in the app or log.
2. Allow the action to run only when no completed action exists for that ID. Configure the search to continue when it finds no result, then use **Filter by Zapier** to control whether the action runs. If found and not-found results need different actions, use [Paths by Zapier](https://help.zapier.com/hc/en-us/articles/8496288555917-Add-branching-logic-to-Zap-workflows-with-Paths).
3. After the action succeeds, save the purchase ID and what completed. Later renewals or instalments for that purchase can then be stopped by the lookup.

If neither the app nor a separate log can support the check, send a task for someone to review and complete manually.

Test with a record you can identify. Check the timing, customer and service, then confirm the action completed in the other app before turning on the Zap.

## Map customer and payment fields

Check the sample values before mapping fields: Zapier may display nested fields with spaces instead of the source names below.

* The customer is `user`: use `user.name` and `user.email`. `offeringUser` is the provider. Newie sends one name field; split it only if the other app requires separate first and last names.
* Before an email or invitation step, check that `user.email` is present and check `user.emailIsUseable`. For `@privaterelay.appleid.com` addresses, Newie sets this flag to false. If the flag is false or you have no direct address, [request the customer's email](/guides/subscribers-customers#request-a-customers-email-address) and use it in the connected app. Apple relay addresses can reject messages from other apps even when Newie emails arrive.
* For payment events, `stripeInvoiceID` identifies the Newie invoice. Save it to match later events and prevent duplicate entries. It is a reference, not an invoice ID created by Xero or QuickBooks.
* The payment `amount` is the invoice total in minor currency units, before payout fees. For AUD or USD, `1060` means `10.60`: divide by 100 before mapping to a decimal amount field. Follow the currency’s [minor-unit rules](https://docs.stripe.com/currencies) for other currencies, and keep the currency with the amount. Use `formattedAmount` for readable message text, not numeric calculations.
* Payment events do not include a dedicated payment-confirmation timestamp. If you log the Zap run time, label it **Date logged**; a subscription start or renewal date is not the bank confirmation date.

## Offering IDs

An Offering ID identifies a Newie service even if its name changes.

On iPhone, open **Sell → Services**, choose the service's `...` menu, open the share sheet and select **Copy Offering ID**. On Mac, or if you prefer a sample, use `offeringID` from a Newie Zap sample for that service.

Add **Filter by Zapier** after the Newie trigger. Continue only when Offering ID **Exactly matches** the copied value.

## Newie trigger events

### Subscription events

These events also apply to instalment plans where the same billing event occurs.

| Trigger                       | When it fires                                                                                          |
| ----------------------------- | ------------------------------------------------------------------------------------------------------ |
| **All Events - Subscription** | Any of the subscription events below                                                                   |
| **Subscription Created**      | The customer first purchases the subscription, even if billing starts later                            |
| **Subscription Started**      | Billing begins and the subscription becomes Active; this does not confirm a bank payment succeeded     |
| **Subscription Renewed**      | Later subscription-cycle or subscription-update invoice activity; a bank debit may still be processing |
| **Subscription Paused**       | The subscription is paused                                                                             |
| **Subscription Ends**         | The subscription or instalment plan reaches its end or a cancellation takes effect                     |

**Subscription Renewed** excludes the initial subscription invoice and separate setup-fee invoices. Use **Payment Paid** when the workflow must wait for confirmed payment.

Scheduling a cancellation does not fire **Subscription Ends**. The event records billing ending, not proof that every invoice was paid. An instalment plan may show **Completed**, **Cancelled** or **Overdue** afterwards. Marking a plan complete after it has already ended does not fire another end event. Check the service terms before using this event to remove access elsewhere.

**Subscription Ends** describes the record identified by `subscriptionID` and `offeringID`, not every service that customer holds. Before archiving a coaching client, removing shared access or clearing a customer-wide Active tag, check their other services. Keep a per-subscription record in your connected tools, or send the event to a person for review if the Zap cannot make that check.

### One-off purchase events

| Trigger                           | When it fires                                                                                          |
| --------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **All Events - One-Off Purchase** | Any available one-off purchase event                                                                   |
| **One-Off Purchase Complete**     | The one-off purchase becomes Active after payment succeeds, including after bank confirmation for BECS |

### Payment events

Payment events cover subscriptions, instalment plans and one-off purchases.

| Trigger                   | When it fires                                                                     |
| ------------------------- | --------------------------------------------------------------------------------- |
| **All Events - Payments** | Payment creation and later Paid, Overdue, Skipped, Uncollectible or Voided events |
| **Payment Paid**          | An invoice payment is confirmed, including a separately collected Setup Fee       |
| **Payment Overdue**       | An invoice becomes overdue because payment has not been collected                 |
| **Payment Skipped**       | An invoice is created during a subscription pause and marked Paused               |
| **Payment Uncollectible** | An unpaid invoice is marked uncollectible after retry handling                    |
| **Payment Voided**        | An invoice is marked Voided                                                       |

**Payment Created** is not offered as a standalone trigger. **All Events - Payments** can include `payment.created` while an invoice is Pending, so inspect **Triggering Event** and filter for the result you need. Use **Payment Paid** for a confirmed-payment workflow across all service types.

<span id="common-zapier-questions" />

## Reports and other connections

Zapier does not send payout reports, payout batches or payout fee breakdowns. Download those from [Payouts](/guides/payouts) or [Reports & Reporting](/guides/reports-reporting). The [Xero](/integrations/newie-xero) and [QuickBooks](/integrations/newie-quickbooks) guides explain reconciliation and per-payment alternatives.

Newie does not currently offer a public self-serve API. For a connection Zapier cannot provide, or a complete data migration, [contact Newie support](/integrations#custom-integrations).

*Last updated: 2026-09-11*