Connect Newie to Zapier
- In Newie, open Settings → Integrations → Connect Zapier. On Mac, open the Integrations tab in Settings. If the option says Zapier Connected, open that instead.
- Choose Set Up if prompted. The API Token appears on this Newie screen; copy it.
- In Zapier, create a Zap and choose Newie as the trigger app.
- Paste the token when Zapier asks you to connect your Newie account.
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.
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 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. UsesubscriptionID 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 or another searchable tool.
- Before the invitation or task action, look up the purchase ID in the app or log.
- 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.
- 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.
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: useuser.nameanduser.email.offeringUseris 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.emailis present and checkuser.emailIsUseable. For@privaterelay.appleid.comaddresses, Newie sets this flag to false. If the flag is false or you have no direct address, request the customer’s email and use it in the connected app. Apple relay addresses can reject messages from other apps even when Newie emails arrive. - For payment events,
stripeInvoiceIDidentifies 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
amountis the invoice total in minor currency units, before payout fees. For AUD or USD,1060means10.60: divide by 100 before mapping to a decimal amount field. Follow the currency’s minor-unit rules for other currencies, and keep the currency with the amount. UseformattedAmountfor 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.
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
Payment events
Payment events cover subscriptions, instalment plans and one-off purchases.
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.