SMS receivedsms.received
WORKFLOW STUDIO · NO-CODE MOBILE AUTOMATION
Turn every mobile event into the right next action.
Workflow Studio connects what happens on your mobiles to what your business should do next. Select an SMS, call, WhatsApp or email event, filter it with precise conditions, and launch one or more actions from a visual workspace—without writing code.
✓Build and test safely before activation. Simulations never send a live SMS, WhatsApp message, email, notification or webhook.
EVENT DATA
Message contains “urgent”data.message
MATCHED
{{data.from}}{{data.device_id}}supported eventsAcross SMS, calls, WhatsApp and email
condition operatorsFrom simple existence checks to regular expressions
action typesMessages, notifications, email and HTTPS webhooks
code requiredConfigure, simulate and activate visually
WHY WORKFLOW STUDIO
Automation that starts with the communication channels you already use.
Incoming messages, missed calls and sending failures often require the same repetitive decisions. Workflow Studio turns those events into consistent processes, so the right response, alert or integration can happen without waiting for someone to monitor every screen.
React faster
Trigger follow-up as soon as a supported event enters SMSMobileAPI instead of relying on manual checks.
Reduce repetitive work
Reuse the sender, message, contact, device or event data directly inside the next action.
Keep decisions consistent
Apply the same keyword, number, status or duration conditions every time.
Connect existing systems
Send a structured HTTPS webhook to your software when a matching mobile event occurs.
Test before going live
Preview every condition result and every resolved action field without executing a real action.
Understand every execution
Review the trigger, condition trace, action state, attempts and error details in one audit log.
THE VISUAL BUILDER
One visual logic: WHEN → IF → THEN.
Each workflow starts with one event, can evaluate up to 20 conditions, and can queue up to 10 actions. Conditions can require all rules or accept any matching rule.
Choose the event
Start from a received SMS, missed call, WhatsApp message, voice transcription, delivery result or email event.
→Filter the right situations
Check whether a field exists, equals, contains, starts with, ends with, is greater or lower, or matches a regular expression.
→Perform one or more actions
Send an SMS, WhatsApp message, email or mobile notification, or call your own HTTPS webhook.
15 EVENT TRIGGERS
Listen to the complete mobile communication lifecycle.
Choose the exact moment that matters. Workflow Studio exposes operational events from the channels connected to SMSMobileAPI.
SMS
5 EVENTS- API submission
- Sent confirmation
- Sending failure
- Received SMS
- SMS sent manually from mobile
Calls
3 EVENTS- Missed call
- Incoming call
- Outgoing call
- Sending submission
- Sent confirmation
- Sending failure
- Received message
- Voice message transcribed
- Email sent
- Email received
PRECISE CONDITIONS
Go from a broad event to an exact business decision.
Conditions inspect the actual event fields. Combine several rules with ALL or ANY logic, choose case-sensitive matching when needed, and use regular expressions for advanced formats.
ExistsDoes not existEqualsDoes not equalContainsDoes not containStarts withEnds withGreater thanLess thanRegular expression
Example: detect an urgent incoming SMS
- Event
- sms.received
- Field
- data.message
- Operator
- contains
- Value
- urgent
- Next action
- Notify the connected mobile and send an acknowledgement SMS
DYNAMIC PLACEHOLDERS
Dynamic data keeps every action personal and useful.
A placeholder is replaced with the real value from the event when the workflow runs. Use the raw field name in a condition, then wrap the same field in double braces inside an action.
CONDITION
data.from→ACTION{{data.from}}{{data.from}}The sender of an incoming SMS or WhatsApp message
{{data.message}}The complete text carried by the event
{{data.number}}The phone number involved in a call
{{data.device_id}}The connected mobile concerned by the event
{{data.contact_name}}The available WhatsApp or mobile contact name
{{data.transcript}}The text generated from a WhatsApp voice message
{{type}}The exact event type that started the workflow
{{occurred_at}}The UTC time when the communication activity happened
Important: If an event does not provide a value, the placeholder becomes empty. Add an “Exists” condition when that information is required.
5 ACTION TYPES
Continue the conversation or connect another system.
Add several actions to one workflow. Fields can contain fixed content, dynamic placeholders, or both.
Send an SMS
Reply to the sender, notify a team member or continue an operational process through a connected mobile.
Send WhatsApp
Queue a WhatsApp response through the linked and active WhatsApp session.
Send an email
Use an email mailbox already configured in the SMSMobileAPI account.
Send a mobile notification
Alert a specific connected SMSMobileAPI mobile using its device identifier.
Call an HTTPS webhook
POST the event and resolved fields to a public HTTPS endpoint in your own application.
AUTOMATION IDEAS
Useful workflows you can build in minutes.
Keyword reply
When an SMS is received and the message contains “INFO”, send the requested information back to the same number.
↗Missed-call follow-up
When a missed call arrives, send an acknowledgement SMS and notify the connected support mobile.
↗WhatsApp escalation
When a received WhatsApp message contains “urgent”, alert a team member and forward the event to your HTTPS endpoint.
↗Failure monitoring
When an SMS or WhatsApp sending operation fails, send an email containing the recipient, source and returned error.
↗Voice-message routing
When a WhatsApp voice message is transcribed, detect a keyword in the transcript and send the text to your business system.
↗Call reporting
When an incoming or outgoing call is synchronized, forward the number, duration and device to your reporting endpoint.
↗SIDE-EFFECT-FREE SIMULATION
Simulate first. Activate only when the result is correct.
The safe simulator creates a realistic sample event, evaluates every condition and resolves every placeholder. It then shows which actions would run—without contacting a recipient or an external endpoint.
- ✓See the received and expected value for each condition
- ✓Confirm whether ALL or ANY condition logic matches
- ✓Preview the final recipient, message, subject or JSON body
- ✓Keep every live side effect disabled during the simulation
{
"type": "sms.received",
"data": {
"from": "+32470000000",
"message": "urgent request"
}
}CONTROL AND OBSERVABILITY
Built for controlled execution, not a fragile browser action.
Active workflows listen for supported Webhook V2 events. Matching actions enter a durable asynchronous queue, keeping the dashboard responsive and allowing the worker to track attempts and failures independently.
Asynchronous actions
Slow external services do not hold open the dashboard request.
Retry-aware queue
Action jobs retain their attempt count, next attempt and final state.
Account isolation
Every workflow, run and action belongs to the authenticated account.
Versioned definitions
Each saved update increments the workflow definition version.
Pause at any time
Keep a workflow editable and testable without letting it react to live events.
Detailed audit trail
Filter executions and inspect condition traces, action results and errors.
EXECUTION LOGKnow why a workflow matched, skipped or failed.
Open execution logs →FOR EVERY TEAM
Made for operations teams and developers alike.
Small businesses
Automate acknowledgements and alerts without building an internal integration platform.
Customer support
Route urgent messages and missed calls to the right person more consistently.
Developers
Connect mobile events to an HTTPS endpoint while leaving common routing rules in the dashboard.
Agencies and integrators
Create repeatable communication logic for customer accounts with visible tests and logs.
WORKFLOW FAQ
Clear answers before your first automation.
Understand events, limits, simulations and execution before activating a live workflow.
Do I need to write code?＋
No for SMSMobileAPI actions and conditions. A developer is only needed if you choose to call a custom HTTPS webhook or connect your own external system.
Can a workflow use several conditions?＋
Yes. One workflow supports up to 20 conditions. You can require all conditions to match or continue when any condition matches.
Can a workflow launch several actions?＋
Yes. One workflow can queue up to 10 actions in the order defined in the visual builder.
Does a simulation send real messages?＋
No. The simulator evaluates conditions and resolves placeholders, but it explicitly prevents every live action.
Where can I see what happened?＋
The execution log shows the event, status, condition trace, asynchronous action attempts, result excerpts and errors.
Can I stop an automation without deleting it?＋
Yes. Pause it to keep the definition available for editing and simulation, then reactivate it when ready.
What happens when event data is missing?＋
The corresponding placeholder resolves to an empty value. Use the Exists condition whenever that field is required by the action.
Are workflows the same as external webhooks?＋
They complement each other. Workflow Studio makes decisions and can perform built-in actions; a webhook action can then pass the matching event to your own application.
FROM EVENT TO ACTION
Make your mobile communication react automatically.
Open Workflow Studio, select the event that matters, add your conditions and actions, run a safe simulation, then activate the workflow when the preview is correct.
