Connect Make

The ReputeCast app for Make is a newsletter integration for scenarios: they start from ReputeCast events, or add contacts, tag them, record events and send transactional email from your other apps. It’s free and uses only ReputeCast’s public API, with a key that can do only what you allow.

Before you begin

• You need integrations:manage (Owner or Admin). Read Connect other tools for how keys, statuses and the call log work.
• Make’s servers call your instance, and ReputeCast calls Make’s webhook addresses for triggers, so ReputeCast must be reachable from the internet over HTTPS. An instance on a private network can’t use Make; use n8n on the same network instead.

What it can do

Module	Kind	ReputeCast	Needs
Watch Subscribed Contacts	Instant trigger	contact.subscribed	subscribers:view
Watch Unsubscribed Contacts	Instant trigger	contact.unsubscribed	subscribers:view
Watch Updated Contacts	Instant trigger	contact.updated	subscribers:view
Watch Form Submissions (any form, or one)	Instant trigger	form.submitted	subscribers:view
Watch Sent Campaigns	Instant trigger	campaign.completed	campaigns:view
Watch Transactional Bounces	Instant trigger	message.bounced	transactional:view
Create or Update a Contact	Action	Names, custom fields, language, tags, lists with single or double opt-in	subscribers:create, subscribers:edit
Add a Contact to a List	Action	Single or double opt-in	subscribers:edit
Add a Tag to a Contact	Action	One or more tags	subscribers:edit
Record an Event	Action	An API event with properties; starts automations	subscribers:edit
Send a Transactional Email	Action	A published template, a recipient, its variables and an optional language	transactional:send (sensitive)

Dropdowns and dynamic fields come from your workspace: lists, published templates, signup forms, custom fields and the chosen template’s variables. Trigger payloads are listed in Webhook events.

Connect Make

1. In ReputeCast, open Settings › , then Integrations, find Make under Automation platforms and choose Connect.

2. Choose what Make 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.

3. In a scenario, add a ReputeCast module and choose Create a connection with:

   • Instance URL: your ReputeCast address without a trailing slash, for example https://reputecast.acme.io.
   • Key: the key from step 2.

4. Saving tests the connection (GET /api/v1/integration). ReputeCast’s connect dialog shows “Make called at 14:31 · Test connection · 200”, and the connection keeps the key’s workspace.

Good to know

• Triggers. Creating a trigger’s webhook in Make registers it in ReputeCast, shown read-only as “Managed by Make” on Settings › , then Webhooks; deleting it in Make removes it. If it’s deleted in Make without detaching, ReputeCast removes it at the next delivery, when Make answers 410 Gone.
• Signatures. ReputeCast signs every delivery (X-ReputeCast-Signature), but Make doesn’t give custom apps a webhook’s raw body, so the app can’t check the signature. A Make webhook’s address is a long random URL: keep it private. Read Receive webhooks.
• Scenario names. Every call carries X-ReputeCast-Workflow with the scenario’s name and ID, so ReputeCast lists the scenarios that use it. Calls without them are listed as “Unnamed scenario”.
• 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. Those bundles end with a DataError in ReputeCast’s words (“rob@example.net left Beta Program on 2 Oct…”). Add an Ignore or Resume error handler to the module so the rest of the scenario keeps running, or turn on “Allow storing of incomplete executions”.
• Idempotency. Send a Transactional Email 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.

Troubleshooting

• InvalidAccessTokenError: the key was revoked or expired. In ReputeCast choose Reconnect and update the connection in Make.
• InvalidConfigurationError with “Change what Make can do in Settings › Integrations”: the action is off for this key. Turn it on in ReputeCast; the key stays the same.
• InvalidConfigurationError with “…take it over…”: the person who connected Make left the workspace. Choose Take over.
• After rotating the key: the old key keeps working for 24 hours. Paste the new key into the connection in that time.

Related

Connect other tools

Connect Zapier

Build an integration

Send transactional email with the API