Integrations · Make
Visual iMessage and SMS automations
Add senderZ modules to any Make scenario. Build visual automations that send iMessage and SMS with conditional routing, batch processing, and error handling — all without writing code.
How it works
- Add senderZ module in Make. Search for "senderZ" in the Make module directory. Add it to a new or existing scenario.
- Authenticate with your API key. Paste your senderZ API key. Make stores it securely and uses it for all scenarios.
- Build your scenario. Connect triggers (webhook, schedule, or any Make-supported app) to senderZ actions. Add routers, filters, and iterators as needed.
- Run on schedule or webhook. Activate the scenario. Make executes on your chosen schedule or fires instantly on webhook triggers.
Use cases
Multi-step routing with conditions
Route messages by recipient type: VIP clients get a dedicated number via iMessage, standard contacts get pooled SMS, international numbers get skipped with a log entry. Make's router handles the branching; senderZ handles the delivery.
Batch contact import + welcome message
Upload a CSV to Google Sheets, Make iterates over each row, creates a senderZ contact, and sends a templated welcome message. Thousands of contacts onboarded in one scenario run.
Error handling with fallback channels
If iMessage delivery fails, Make's error handler catches the failure and re-routes to SMS via a second senderZ module. The recipient gets the message regardless of which channel succeeds.
What you get
Send Message module
Send iMessage or SMS from any Make scenario. Map recipient, body, channel, and template from upstream modules.
List Messages module
Retrieve recent messages by tenant, recipient, or status. Use it to build dashboards or sync delivery data to external systems.
Webhook trigger module
Receive senderZ events (delivered, failed, inbound, read) as Make webhook triggers. Real-time — no polling.
Template variable mapping
Reference senderZ templates by ID and map Make data to template variables. Type-safe — missing variables return a clear error.
Error handling with retry
Make's built-in error handlers work with senderZ modules. Configure retry count, fallback routes, or break scenarios on specific error codes.
Frequently asked questions
Make vs Zapier for senderZ — which should I use?
Both work. Make is better for complex multi-branch scenarios with conditional logic and data transformation. Zapier is simpler for straightforward trigger→action workflows. senderZ supports both equally.
Are there scenario execution limits?
Make limits depend on your Make plan (operations/month). Each senderZ module call counts as one Make operation. On the senderZ side, your plan's new-contact daily cap applies as usual.
Does it support Make's data stores?
Yes. You can read from and write to Make data stores in the same scenario that sends senderZ messages. Use data stores to track sent-message IDs, deduplicate recipients, or maintain conversation state.
Can I process batches?
Yes. Use Make's iterator module to loop over a list of recipients, then send a senderZ message for each. Make handles the iteration; senderZ handles the delivery. Rate limits apply per your senderZ plan.
Build your first scenario
14-day free trial. No credit card. No code.