Skip to main content
Make (formerly Integromat) is a no-code automation platform. The Senderz app for Make lets you build scenarios that react to Senderz events and act on your workspace — no code, no server. Every module is backed by the Senderz Public API, so anything the app does, you can also do directly from the API or a generic HTTP call.
The official Senderz app for Make is rolling out through Make’s partner review. Until it’s listed, you can build the same automations today using Make’s HTTP modules against the endpoints documented here, and subscribe to events via outbound webhooks.

​
Connect your workspace

The Senderz connection in Make authenticates with your workspace ID and an API key.
1

Get your workspace ID

In Senderz, your Workspace ID is the workspace slug shown in Settings. You send it as the X-Sender-Tenant header.
2

Mint an API key

An owner or admin creates a key from Settings → Integrations (or POST /integrations/event-ingest-key). Copy it — it’s the X-API-Key.
3

Create the connection

In Make, add a Senderz module, create a new connection, and paste both values. Make validates it against GET /public/me and shows your workspace name on the connection chip.
Treat the API key like a password. It grants profile management, transactional send and webhook management on your workspace. Rotate it if it leaks (delete and re-issue from Settings → Integrations).

​
Triggers (instant)

Instant triggers fire from Senderz outbound webhooks. When you add a trigger, Make registers a webhook subscription for you (via POST /public/webhooks) and removes it when you delete the module.

Profile created

Fires on contact.created.

Profile updated

Fires on contact.updated.

List subscribed / unsubscribed

Fires on list.subscribed / list.unsubscribed.

Email opened / clicked

Fires on email.opened / email.clicked.

Order & shipment events

order.* and shipment.* for lifecycle automations.

Custom event

Any event you send to /events/ingest.
See the full event vocabulary (29 types).

​
Actions

Actions call the Senderz Public API. Every merchant-facing action is keyed by email, never a contact UUID — the UUID stays available for advanced callers.

​
Update a Profile — parameters

All optional except Email (the lookup key). Native fields write to their column; everything else merges into custom properties.
Email (lookup), New email (rename), Phone, First name, Last name, Timezone, Language (locale).
Tags (array), Notes, City, Country, State/Province, Zip, Address, Address line 2, Date of birth, Gender, Job title, and any Custom properties (key/value).

​
Universal “Make an API call” module

For anything not covered by a dedicated module, use the generic call module. It signs the request with your connection and lets you hit any public endpoint:
The base URL is https://api.senderz.app/api/v1; your connection adds the X-Sender-Tenant and X-API-Key headers automatically.

​
Pagination in Make

List modules and search RPCs page with limit + offset. The response carries has_more and a next_cursor (a stringified offset). Make follows the cursor for you.
Make caps a module run at 40 seconds, 100 requests and 3,200 records. The Senderz list endpoints are database-paginated and default to a limit of 50 (max 100), which fits comfortably inside Make’s limits.

​
Example scenarios

Trigger on a new row in your CRM → Upsert a Profile by email → Add to List (your newsletter segment).
Trigger on an event in another tool → Send SMS with the recipient and body. The send is wallet-gated and uses your approved sender ID.
Email opened trigger → transform → write to BigQuery / Sheets.
Trigger on a subscription renewal → Send Event (renewal) with properties → a Senderz flow enrolled on that custom event does the rest.

​
Reference