We use optional, privacy-safe analytics to understand which pages help visitors. Nothing optional runs until you choose. Privacy policy

Skip to content
SendiMessage
Start Pilot
Guide AvailableAutomation Platform

Send messages from Make scenarios

Make (formerly Integromat) builds visual scenarios with fine-grained data mapping, and its generic HTTP module ('Make a request') is a first-class citizen — ideal for APIs without a dedicated app.

Add the HTTP module after your trigger: method POST, the send-message URL, X-API-Key and X-API-Secret headers, and a JSON body mapped from earlier modules with Make's mapping panel. Parse the response to branch on status. A custom webhook module gives you a URL to register as your SendiMessage event endpoint, so delivery confirmations and replies can drive the rest of a scenario — updating a CRM row, posting to a channel, or opening a ticket.

Request This SetupBook an Integration Review

What this integration enables

CRM triggers without code
Bridge CRM record changes to messaging with a Make scenario instead of middleware.
Form and lead follow-up
New form submissions get a confirmation or next-step message.
E-commerce notifications
Order events from your store platform become customer updates.
Reply routing
SendiMessage webhooks trigger Make flows that write replies into your CRM or helpdesk.

Implementation options

the HTTP 'Make a request' module
Configure the request: POST https://api.sendimessage.com/v1/send-message, X-API-Key and X-API-Secret headers from the platform's credential store, and a JSON body mapped from trigger data.
Webhook trigger for events
Give SendiMessage a Make webhook URL as your event endpoint, and delivery/reply events start flows that update your other systems.

Architecture

How it fits together: Make event, then Workflow or backend, then SendiMessage API, then Managed messaging line, then SMS or supported iMessage, then Customer, then Delivery or reply event, then Signed webhook, then Make timeline update.
  1. Make eventA record changes, a stage moves, or a workflow fires
  2. Workflow or backendMake automation or your middleware prepares the request
  3. SendiMessage APIPOST /send-message — the message is validated and queued
  4. Managed messaging lineYour dedicated line sends the message
  5. SMS or supported iMessageChannel routing picks iMessage where supported, SMS otherwise
  6. CustomerThe message arrives; the customer can reply
  7. Delivery or reply eventSendiMessage records what actually happened
  8. Signed webhookYour endpoint receives outbound or receive
  9. Make timeline updateYour handler writes the event back as activity

Example request

HTTP action body
{
  "number": "{{trigger.phone}}",
  "content": "Hi {{trigger.first_name}}, your appointment is tomorrow at 10:00 AM.",
  "status_callback": "https://your-endpoint.example.com/status?record_id={{trigger.id}}"
}

Map the {{…}} placeholders from your Make trigger data — the syntax shown is illustrative. status_callback is optional: it receives this message's delivery events, and because you compose the URL you can embed your own record id for correlation. Store the returned message_handle for the same purpose.

Delivery events and incoming replies

Use a Make webhook trigger as your SendiMessage event endpoint: delivery confirmations and incoming replies then start flows that update the CRM, notify a channel, or open a ticket.

webhook event
// "outbound" event → your make endpoint
// Verify the SendiMessage-Signature header (t={timestamp},v1=HMAC-SHA256 of
// "{timestamp}.{raw body}", keyed with your webhook secret), then use
// GET /v2/messages/{message_handle} for authoritative state and match it to
// your record_id in make.

Limitations and honest notes

  • iMessage delivery is available on supported messaging lines and destinations. Recipients without iMessage receive SMS when fallback is configured — never assume universal iMessage availability.
  • Messages are accepted asynchronously — the API returns status QUEUED and final status arrives via webhook or the message endpoints.
  • No official SDK for this ecosystem yet — the example uses plain HTTP against the REST API. Official SDKs are published for JavaScript/TypeScript (npm: sendimessage), Python (PyPI: sendimessage), PHP (Composer: sendimessage/sdk), and Go (github.com/sendimessage/sendimessage-go). Every SDK is dependency-free and covers the full public API surface.
  • A published SendiMessage app in the Make directory is not available today — the integration uses the HTTP 'Make a request' module, which is fully supported.

Security considerations

  • Store the API key in Make's credential/connection store, not in plain text fields inside scenarios.
  • Restrict who can edit flows that send customer messages.
  • Keep phone numbers and message content out of run logs where the platform allows it.

Frequently asked questions

Is there a SendiMessage app in the Make directory?
Not yet — statuses on this site only claim a published app when one has actually shipped. the HTTP 'Make a request' module works today with the configuration on this page, and it exposes the full API.
What does a successful send look like?
The API responds with status "QUEUED" plus a message_handle you can store for correlation. Treat non-2xx responses as failures in your flow's error path.
Can flows react to delivery and replies?
Yes — register a Make webhook URL as your SendiMessage event endpoint, and outbound / receive events become flow triggers.

Ready to connect Make?

Request a messaging line and a SendiMessage integration specialist will review your Make workflow and guide the setup.