Connect n8n
n8n-nodes-reputecast is the n8n newsletter node package for ReputeCast: the ReputeCast Trigger node starts
workflows from ReputeCast events, and the ReputeCast node adds contacts, tags them, records events and sends
transactional email. The nodes are free, work with self-hosted n8n (and n8n Cloud once n8n has verified them) and use
only ReputeCast’s public API.
Before you begin
Section titled “Before you begin”- You need
integrations:manage(Owner or Admin). Read Connect other tools for how keys, statuses and the call log work. - n8n only needs to reach your instance for actions, so n8n and ReputeCast can share a private network. Triggers go the other way (ReputeCast posts events to n8n): see n8n on a private network.
What it can do
Section titled “What it can do”ReputeCast Trigger starts a workflow when:
| Event | ReputeCast event | Needs |
|---|---|---|
| Contact Subscribed | contact.subscribed |
subscribers:view |
| Contact Unsubscribed | contact.unsubscribed |
subscribers:view |
| Contact Updated | contact.updated |
subscribers:view |
| Form Submitted (any form, or one) | form.submitted |
subscribers:view |
| Campaign Sent | campaign.completed |
campaigns:view |
| Transactional Message Bounced | message.bounced |
transactional:view |
Activating the workflow creates a webhook in ReputeCast, shown read-only as “Managed by n8n” on Settings, then Webhooks; deactivating it removes it. Every delivery is checked against the webhook’s signing secret: one that doesn’t match, or is more than 5 minutes old, is refused and starts nothing.
ReputeCast does:
| Resource › Operation | What it does | Needs |
|---|---|---|
| Contact › Create or Update | Matches by email; sets names, custom fields, language and tags; adds to lists with single or double opt-in | subscribers:create, subscribers:edit |
| Contact › Add to List | Single or double opt-in | subscribers:edit |
| Contact › Add Tag | One or more tags | subscribers:edit |
| Event › Record | An API event with properties; starts the automations that listen for it | subscribers:edit |
| Transactional Email › Send | A published template, a recipient, its variables (mapped field by field) and an optional language | transactional:send (sensitive) |
n8n’s AI Agent can use the ReputeCast node as a tool. It can do only what the key may do, and sending transactional email starts off when you connect n8n.
Install the nodes
Section titled “Install the nodes”In n8n, open Settings › Community nodes › Install, enter n8n-nodes-reputecast and confirm. Self-hosted n8n can
also install them with npm install n8n-nodes-reputecast in ~/.n8n/nodes. On n8n Cloud, the nodes appear in the nodes
panel once n8n has verified them.
Connect n8n
Section titled “Connect n8n”-
In ReputeCast, open Settings, then Integrations, find n8n under Automation platforms and choose Connect.
-
Choose what n8n may do. Send a transactional email starts off because it needs the sensitive
transactional:send. Choose Create key and copy the key (rc_live_…); it’s shown once. -
In n8n, add a ReputeCast API credential with:
- Instance URL: your ReputeCast address, for example
https://reputecast.acme.io. - Key: the key from step 2.
- Instance URL: your ReputeCast address, for example
-
Save. n8n tests the connection (
GET /api/v1/integration), and ReputeCast’s connect dialog shows the call arriving. The credential learns which workspace the key belongs to and keeps it.
n8n on a private network
Section titled “n8n on a private network”When n8n runs on a private address (for example n8n.acme.internal), ReputeCast refuses to post trigger events to it
until an operator allows webhooks to private addresses with
webhooks.allow_private_networks (REPUTECAST_WEBHOOKS__ALLOW_PRIVATE_NETWORKS=true).
Actions work either way. Read Security and hardening before you turn it on.
Good to know
Section titled “Good to know”- Workflow names. Every call carries
X-ReputeCast-Workflow: <workflow name>; id=<workflow ID>, so ReputeCast lists the workflows that use it, with their calls and errors, on its n8n page. - Consent is kept. ReputeCast never adds someone back to a list they left, never adds a suppressed address and
doesn’t send transactional email to one. Such an item comes out as
{ "skipped": true, "code": "unsubscribed", "reason": "rob@example.net left Beta Program on 2 Oct…" }, and the workflow carries on with the other items. - Errors in ReputeCast’s words. Other refusals fail the node with ReputeCast’s sentence: a missing template variable, an action turned off (“Change what n8n can do in Settings › Integrations”), a revoked key (“Reconnect n8n…”) or a key whose owner left (“…take it over…”). Turn on Continue On Fail to keep going instead.
- Idempotency. Transactional Email › Send takes an optional Idempotency Key, such as the triggering event’s ID. ReputeCast sends nothing new when the same value comes again within 24 hours.
- Rotating the key in ReputeCast keeps the old one working for 24 hours: paste the new one into the credential in the meantime.
Troubleshooting
Section titled “Troubleshooting”- A trigger never fires: check that the workflow is active and that the webhook is listed on Settings, then Webhooks. For n8n on a private address, see n8n on a private network.
- “Reconnect n8n…”: the key was revoked or expired. Choose Reconnect in ReputeCast and paste the new key into the credential.
- “…take it over…”: the person who connected n8n left. Choose Take over.