n8n

Use the Synci community node in n8n to start workflows on new transactions, balance updates and connection events, and to read accounts, balances, holdings and transactions from any workflow.

Written By Matias

Last updated About 2 hours ago

n8n is a workflow automation tool you can use in the cloud or host yourself. With the Synci nodes for n8n, you can start a workflow whenever something happens in Synci, and read or change your Synci data from any workflow.

n8n works a little differently from our other destinations. You build workflows on n8n's side. When a workflow with the Synci Trigger is turned on, it creates its own webhook in Synci, and removes it again when you turn the workflow off. There is nothing to set up in Synci first.

What you get

Synci Trigger: starts a workflow when Synci sees new transactions, balance changes, account changes or connection events.
Synci: reads accounts, balances, holdings, connections and transactions, and can add, edit and delete transactions.

Installing the Synci node

The Synci nodes are an n8n community node package called @synci/n8n-nodes-synci.

n8n Cloud and self-hosted n8n: open the nodes panel, search for Synci and install it.
Self-hosted n8n, by package name: follow n8n's community nodes installation guide and enter @synci/n8n-nodes-synci.

Connecting your Synci account

Both nodes have an Authentication field with two options.

OAuth2 (n8n Cloud)

In n8n, create a Synci OAuth2 API credential and click Connect my account.
Sign in to Synci and choose which accounts n8n can see. There is nothing else to fill in.

This option only works on n8n Cloud. On a self-hosted n8n, use an API token.

API Token (works everywhere)

In Synci, go to Developers > API tokens and create a token.
Under Permissions, choose Full access, or grant only what your workflows use:
- accounts:read: accounts, balances and holdings
- transactions:read and transactions:write: reading and changing transactions
- financial-connections:read: connections
- webhooks:read and webhooks:write: the Synci Trigger
- profile:read: needed for n8n's Test button on the credential
Choose which accounts the token can access, give it a name, and copy the token. You won't be able to view it again.
In n8n, create a Synci API credential and paste the token.

Synci Trigger

Pick one or more Events to listen for. Under Options, you can also set:

Account IDs: only trigger for these accounts, separated by commas. Leave it empty for all accounts.
Simplify: output only the event data, without the delivery envelope (event type, event ID and timestamp).

When you activate the workflow, the trigger registers a webhook with your Synci account. When you deactivate it, the webhook is removed again. While it exists, you'll find it in Synci under Developers > Webhooks with an n8n badge.

Clicking Listen for test event in n8n sends a sample of the first selected event straight away, so you can build the rest of your workflow on real-looking data.

Available events

Event	Fires when
Transactions Created	New transactions were fetched from the bank
Transactions Updated	Pending transactions were booked or changed
Balance Updated	A new balance was fetched for an account
Holdings Updated	Investment or crypto positions were refreshed
Account Created	A new bank, investment or crypto account was added
Account Updated	An account was renamed or its details changed
Account Deleted	An account was removed
Connection Created	A bank connection was started
Connection Activated	A bank connection finished authorization and is live
Connection Reauthorized	The bank consent for a connection was renewed
Connection Expiring	The bank consent for a connection expires soon
Connection Expired	The bank consent for a connection has expired
Connection Failing	Syncing a bank connection has started to fail
Connection Recovered	A failing bank connection is syncing again
Connection Disabled	A bank connection stopped syncing after repeated failures
Connection Deleted	A bank connection was removed

Good to know

Signatures are checked for you. Every delivery is signed, and the trigger rejects anything without a valid X-Synci-Signature header.
Retries. If a delivery fails, Synci retries after 1 minute, 10 minutes and 1 hour. The event_id stays the same across retries, so use it to skip duplicates.
Plan limits. Each active trigger uses one webhook endpoint, which counts towards your plan's webhook limit. See synci.io/pricing.
HTTPS only. Synci only delivers to HTTPS URLs, so a self-hosted n8n needs a public HTTPS address.

For more on payloads and delivery, see Webhooks.

Synci node

Resource	Operations
Account	Get, Get Many, Get Balances, Get Holdings
Connection	Get, Get Many
Transaction	Create, Delete, Get, Get Many, Update

Get Many has a Return All toggle and a Limit. Transactions can be filtered by account, booking date range, booked only, and free-text search, and sorted by date or amount.
Create adds a transaction to a manual account.
Simplify is on by default and returns a short version of each account, balance, holding, transaction or connection. Turn it off to get every field Synci returns.
n8n AI agents can use the Synci node as a tool.
Output rules. If an account has output rules, they shape what the Synci Trigger receives, and what the Synci node reads when you connect with OAuth2. With an API token, the Synci node reads your data exactly as it is stored in Synci.

Ideas to get you started

Spending alerts: Synci Trigger (Transactions Created), then an IF node for amounts below -100, then a Slack message.
Transaction log: Synci Trigger (Transactions Created, Simplify on), then append a row to Google Sheets.
Daily balance digest: a Schedule Trigger, then Synci (Account: Get Many), then an email summary.
Reconnect reminders: Synci Trigger (Connection Expiring), then an email with a link to renew the bank connection.

Troubleshooting

What you see	What it means and how to fix it
"Synci refused to create the webhook"	Your plan has no free webhook slot, or your API token is missing the `webhooks:write` permission. Free up a webhook under Developers > Webhooks, or give the token that permission.
The OAuth2 credential doesn't work on a self-hosted n8n	Sign in with Synci only works on n8n Cloud. Use the Synci API credential with an API token instead.
The trigger never fires on a self-hosted n8n	Synci must be able to reach your n8n over public HTTPS. Make sure your n8n's webhook URL is a public HTTPS address.
The credential's Test fails	The token needs the `profile:read` permission, or Full access.
The same event runs a workflow twice	A delivery was retried. Skip events whose `event_id` you have already handled.

Need a hand? Reach out to us any time. We're happy to help you wire up your first workflow.

Was this helpful?

Still need help? Ask the team