Working in the inbox

Automate with n8n

Start n8n workflows on new messages and send messages from any workflow.

n8n is a workflow automation tool. With the STS Connect nodes for n8n you can start a workflow when a message arrives in your inbox, and send messages, update conversations, or save contacts from any workflow.

What you need

  • A self-hosted n8n instance (community nodes are installed by the instance owner), reachable from the internet over HTTPS so the inbox can deliver webhooks to it.
  • An administrator account in the STS Connect Inbox.

Install the nodes

  1. In n8n open Settings → Community Nodes → Install.
  2. Enter n8n-nodes-stsconnect and confirm.

Two nodes appear: STS Connect (send messages, manage conversations and contacts, read inboxes, labels, teams and agents) and STS Connect Trigger (start a workflow on inbox events).

Create an API key

  1. In the inbox open Settings → API & webhooks and create a key.
  2. Choose Read if the workflow only reads data, or Read and write if it sends messages or changes conversations and contacts.
  3. Copy the key straight away: it is shown only once.

In n8n create an STS Connect API credential with the key and your Account ID (the number in the inbox address, after /app/accounts/). Leave the base URL as it is.

Start a workflow on new messages

  1. Add the STS Connect Trigger node, pick the events you want, and activate the workflow. If the workflow sends replies, turn on Options → Only Incoming Messages; otherwise your own replies start the workflow again.
  2. Copy the node's Production URL (the Test URL only works while you test in the editor).
  3. In the inbox open Settings → API & webhooks → Webhooks → Add webhook, paste the URL, and tick the same events.
  4. Press Show secret on the new webhook and paste the secret into the node's STS Connect Webhook credential.

Every delivery is signed. Deliveries with a wrong signature, or older than 5 minutes, are refused before they reach your workflow.

Notes

  • The key acts for your account, not for one person. Delete it in API & webhooks when a workflow is retired.
  • A read key cannot send messages: those calls fail with 403.
  • The node source and full reference are public on GitHub.

Still stuck?

Email hello@stsconnect.chat with your company name and what you were trying to do. We answer on business days.