payments

Stripe integration

Stripe knows the moment money arrives, fails or goes back out. Syncline turns each of those events into something your team can see and act on within a couple of minutes.

Connect Stripe

See all integrations

2870flows running

11 mintypical setup

640000events a month

What Syncline does with Stripe

<p>Stripe processes payments, subscriptions and refunds, and it records each one in detail. Almost every event it emits is interesting to somebody who does not log into Stripe: a first payment means onboarding, a failed charge means a phone call, a refund means a conversation happened that nobody wrote down.</p><p>Syncline listens for the events you choose and routes them onward. A successful payment can create a contact, advance a deal, open a task card and post a line in chat, all from the same trigger, with the customer email carried through so the records connect to each other.</p><p>Money needs handling with care, so the mapping is explicit. Stripe reports amounts in minor units, meaning a charge of forty nine dollars arrives as 4900. Syncline converts it to a decimal with the right currency before writing, and the run history shows both numbers so a finance person can check the arithmetic.</p><p>We read from Stripe and write only what a flow needs to write, such as customer metadata or an invoice. Refunds and charges are never initiated automatically without an explicit action in a flow you built, and those actions are listed on the flow before you turn it on.</p>

Triggers and actions

A trigger starts a flow. An action is what Syncline does next.

Triggers in Stripe

<dl class="sy-deflist"><dt>Payment succeeded</dt><dd>Fires on a completed charge, with the amount, currency, customer and description available.</dd><dt>Payment failed</dt><dd>Fires when a charge is declined, including the reason code so the follow-up can be specific.</dd><dt>New customer created</dt><dd>Fires the first time a customer object exists, which is usually the start of a relationship.</dd><dt>Subscription created or changed</dt><dd>Fires on a new plan, an upgrade, a downgrade or a cancellation, with the old and new plan named.</dd><dt>Refund issued</dt><dd>Fires when money goes back, so support and finance both learn about it without asking.</dd></dl>

Actions in Stripe

<dl class="sy-deflist"><dt>Create a customer</dt><dd>Adds a customer record with email, name and metadata mapped from the source app.</dd><dt>Create an invoice</dt><dd>Draws up an invoice with line items you supply, left as a draft or finalised as you choose.</dd><dt>Find a customer by email</dt><dd>Looks up an existing customer so later steps update rather than duplicate.</dd><dt>Update customer metadata</dt><dd>Writes your own reference IDs onto the Stripe record, which makes later reconciliation trivial.</dd><dt>Issue a refund</dt><dd>Returns a charge in full or in part. This action is off unless you add it deliberately to a flow.</dd></dl>

Fields you can map

<div class="sy-table-wrap"><table><thead><tr><th>Field</th><th>Type</th><th>What it holds</th></tr></thead><tbody><tr><td>Customer email</td><td>email</td><td>The address on the customer object, and the value most flows use to match records elsewhere.</td></tr><tr><td>Amount</td><td>currency</td><td>Reported by Stripe in minor units and converted by Syncline into a decimal before writing.</td></tr><tr><td>Currency</td><td>string</td><td>A three letter code such as usd or eur, kept beside the amount so nothing is assumed.</td></tr><tr><td>Status</td><td>select</td><td>The charge or subscription state, for example succeeded, pending, past_due or canceled.</td></tr><tr><td>Created</td><td>datetime</td><td>The event time as a UTC timestamp, converted for display in your own timezone.</td></tr><tr><td>Invoice ID</td><td>string</td><td>The invoice reference, handy for putting a payable link into an email or a card.</td></tr></tbody></table></div>

Popular Stripe automations

<ul><li>Create a HubSpot contact on the first successful payment</li><li>Alert a Slack channel when a payment fails</li><li>Add every charge to an Airtable revenue base</li><li>Open a Trello onboarding card for each new subscription</li><li>Log refunds as rows in a Notion finance database</li></ul>

Connecting your Stripe account

Authentication OAuth 2.0 with restricted keys

What we ask for Connect through Stripe Connect and Syncline receives a restricted key scoped to the objects your flows use. We ask for read access by default, and write scopes appear only when a flow contains an action that needs them.

Rate limits Stripe typically allows around one hundred read requests per second in live mode, and Syncline works from event notifications rather than polling so the budget stays free.

Questions about Stripe

<div class="sy-faq"><details><summary>Does Syncline ever move money on its own?</summary><div>No. Reads happen automatically, and the only write actions that touch money are ones you added to a flow yourself. They are listed on the flow before you enable it.</div></details><details><summary>How are amounts converted?</summary><div>Stripe sends minor units, so 4900 becomes 49.00 with the currency attached. Both values appear in the run history for checking.</div></details><details><summary>Can I use test mode first?</summary><div>Yes, and we recommend it. Connect the test account, run a few charges through the flow, then swap the connection to live when the mapping looks right.</div></details><details><summary>What about currencies with no decimal places?</summary><div>Currencies such as yen are handled without a false division. The run history names the currency rule that was applied.</div></details><details><summary>How fast does an event reach the next app?</summary><div>Stripe pushes events to us, so the typical gap between a charge and a Slack message or a CRM update is a few seconds.</div></details></div>

Other integrations

Stripe

Stripe knows the moment money arrives, fails or goes back out. Syncline turns each of those events into something your team can see and act on within a couple of minutes.

Trello

Trello is the task board people actually keep updated, because moving a card takes one second. Syncline creates those cards from other systems and reports back when they move.

Airtable

Airtable is where teams build the tracker no off-the-shelf tool provides. Syncline keeps that base fed from your other apps and sends its rows onward when something changes.

HubSpot

HubSpot is the record of who your customers are and how far along they got. Syncline feeds it from the places leads actually arrive, and pushes deal changes back out to the team.

Gmail

Plenty of work still arrives as an email and stays there. Syncline turns matching messages into records in your other apps, and sends mail back out when something changes.

Slack

Slack is where a team notices things, which makes it the best place to put an alert and the worst place to store one. Syncline sends messages into channels when something happens elsewhere, and turns the replies worth keeping into records.

Notion

Notion holds the pages and databases most teams treat as their second brain. Syncline reads those databases on a schedule and writes rows back, so a page never has to be retyped somewhere else.

Start with Stripe today

Build your first Stripe flow in about 11 minutes. No card needed for the free plan.

Start free