Integrations

How Newie connects to other tools through Zapier and supported integrations.

Newie can connect to other tools in two main ways: Zapier automations and direct integrations.

Zapier integrations

Use no-code Newie triggers to send customer, purchase, subscription, and payment events into another app.

Direct integrations

Use this path when the workflow needs Newie support, partner setup, native integration, or code-level work.

Most tool pages in the sidebar integration categories currently show Zapier workflows because Zapier is the main self-serve integration option today. Direct integrations are kept separate because they may require Newie support, partner access, or a different setup path.

Zapier Integrations

Zapier is a no-code automation tool that connects Newie events to other services. Set up the connection once, choose a trigger event, then connect it to an action in another app.

Use Zapier when the workflow starts from something that happens in Newie, such as a customer buying a service, a subscription starting, a payment becoming paid, or an invoice becoming overdue. Zapier is usually the right path for sending customer details to another app, creating a row, adding a tag, posting a message, sending an email, or starting an onboarding workflow.

Connecting Newie to Zapier

1. Open Zapier settings in Newie

   Open Newie → Settings → Integrations → Zapier.

2. Copy the API Token

   Copy the API Token.

3. Create a Zap

   Go to zapier.com and create a new Zap.

4. Choose Newie as the trigger app

   Search for Newie as the trigger app.

5. Connect the token

   Paste the API Token when prompted.

6. Choose the trigger event

   Choose the Newie trigger event that matches the workflow. Use Subscription Created for the initial subscription purchase, Subscription Started for subscription-backed paid access when billing starts, One-Off Purchase Complete for one-off purchases, and Payment Paid for workflows that should wait for confirmed payment. For BECS Direct Debit, Payment Paid fires after bank confirmation, not at initial payment submission.

7. Configure the action

   Configure the action in the connected app and confirm the required action fields are available in that connected Zapier account.

Zapier Events Reference

Newie provides Zapier triggers only. Use Newie as the trigger app, then configure the action in the connected app.

Triggers cover customer, subscription, purchase, and payment events. Newie does not send payout reports, payout batches, or payout fee breakdowns through Zapier. For payout reports and tax exports, use Payouts in Newie.

Third-party actions can vary by app version, account plan, permissions, and workspace setup. Before turning on a Zap, confirm the exact action and required fields appear inside the connected Zapier account.

Subscription Events

Sent when an event related to a subscription occurs. These events can also apply to installment plan activity because installment plans are powered by subscriptions.

Trigger Name	Description
All Events - Subscription	Triggers when any event related to a subscription occurs. This can include relevant installment plan activity where Zapier exposes it through subscription events.
Subscription Created	Triggers when the customer first purchases the subscription. It can fire before billing starts if the subscription has a future start date. This can also apply to installment plan purchases where Zapier exposes the plan through subscription events.
Subscription Started	Triggers when subscription billing actually starts and the subscription becomes active. Use this for subscription-backed paid access, including installment plans, especially when a customer purchased earlier with a future start date.
Subscription Renewed	Triggers when a payment against a subscription invoice succeeds. Use it for subscription-specific renewal workflows, including subscription-backed installment plan activity where relevant. For accounting, fulfilment, or confirmed-payment workflows across all service types, use Payment Paid instead.
Subscription Paused	Triggers when a subscription is paused.
Subscription Ends	Triggers when a subscription moves into Expired, or when an installment plan moves into Completed. It does not fire just because a cancellation has been scheduled.

One-Off Purchase Events

Sent when an event related to a one-off purchase occurs.

Trigger Name	Description
All Events - One-Off Purchase	Triggers when any one-off purchase event involving a customer takes place.
One-Off Purchase Complete	Triggers when a customer makes a one-off purchase.

Payment Events

Sent when a payment event occurs, regardless of whether the payment is for a one-off purchase, subscription, or installment plan.

Trigger Name	Description
All Events - Payments	Triggers when any visible payment event for a subscription, installment plan, or one-off purchase occurs: Paid, Overdue, Skipped, Uncollectible, or Voided. It does not include Payment Created.
Payment Paid	Triggers when a payment is complete for a subscription, installment plan, or one-off purchase. This is the general confirmed-payment trigger and is the best choice for accounting, fulfilment, receipts, and workflows that should run after money is confirmed. For BECS Direct Debit, this fires when the bank confirms the payment and it moves from Pending/Processing to Paid, usually up to 3 business days after submission.
Payment Overdue	Triggers when an invoice for a subscription, installment plan, or one-off purchase becomes overdue after payment has not been collected.
Payment Skipped	Triggers when a scheduled subscription invoice is created during a pause and marked as Paused.
Payment Uncollectible	Triggers when payment can no longer be collected after retry handling for a subscription, installment plan, or one-off purchase.
Payment Voided	Triggers when an invoice or payment record is manually voided for a subscription, installment plan, or one-off purchase.

Direct Integrations

Direct integrations are for workflows that need a deeper connection than Zapier. They are not self-serve in the same way Zapier is.

Use this path when Zapier cannot expose the required action, when the workflow needs code-level access, or when the business needs a supported native, partner, or custom setup.

Newie does not currently offer a public self-serve API. For deeper integration needs, contact Newie support to discuss what is available.

Common Integration Questions

How do I connect Newie to Zapier?

Go to Settings → Integrations → Zapier → Set Up, copy the API Token, then use Newie as the trigger app in Zapier.

Where do I find my API Token?

Go to Settings → Integrations → Zapier. Stripe must be connected before the token is available.

Are the tool guides Zapier-specific?

Mostly, yes. Unless a page clearly says otherwise, the current tool guides explain Zapier workflows where Newie is the trigger app and the connected tool is the action app. Direct or custom setup notes can be added to those tool pages as they become available.

Does Newie have a public API?

Not currently. For self-serve integrations, use Zapier. For deeper or code-level integration needs, contact Newie support.

How do I get my Stripe Express account ID?

Contact Newie support. The team can provide the connected Stripe Express account ID where needed for advanced integrations or custom dashboard setup.

Where should Xero or QuickBooks setup questions live?

Use the dedicated Newie + Xero or Newie + QuickBooks pages. They cover the recommended payout-report workflow and the lower-volume Zapier alternatives.

Where should export and data migration questions live?

Use Reports & Reporting for sales, payout, customer, subscriber, one-off purchase, and installment plan exports. For complete data migration, contact support.

Last updated: 2026-05-31