WORKFLOW STUDIO · NO-CODE MOBILE AUTOMATION
Automate what happens when you receive a call, SMS, WhatsApp
Tell Workflow Studio: “When this happens, and only in these conditions, do that.” It monitors supported SMS, call, WhatsApp and email events, applies your rules, then reacts for you.
✓Build and test safely before activation. Simulations never send a live SMS, WhatsApp message, email, notification or webhook.
{{data.from}}{{data.device_id}}AI WORKFLOW AGENT
Describe the automation. Let the AI agent build the workflow.
Simply explain what you want your mobile to do. The agent asks only the useful questions, understands your answers and prepares the complete workflow for review in Workflow Studio.
- No workflow expertise or technical vocabulary required
- Clear questions guide you through every missing detail
- A ready-to-review workflow is prepared in just a few minutes
When I miss a customer call during opening hours, send a reassuring SMS.
What are your opening hours?
Monday to Friday, from 09:00 to 17:00.
Perfect. I have everything I need. I am creating the workflow now.
WORKFLOW
A workflow is a simple rule that runs automatically.
It tells SMSMobileAPI what to do when something happens. You choose the event, optional conditions and the action. Once active, it watches and reacts for you.
Example: when an SMS contains “URGENT”, notify your team and send an automatic reply.
WORKFLOW STUDIO, SIMPLY
Your mobile events trigger the right action automatically.
A customer calls during opening hours and you miss the call. Workflow Studio can immediately send an acknowledgement SMS and notify your team—without anyone watching the dashboard.
WORKFLOW STUDIO PREVIEW
See the complete workflow before you activate it.
Workflow Studio keeps the trigger, availability schedule, conditions and actions together in one clear workspace. Every block can be edited, tested and reviewed without losing sight of the complete automation.
call.misseddata.number = +1 202 555 ••••POST /office/alertAvailability
Events outside this schedule are skipped and explained in the execution log.
MOBILE WORKFLOW CONTROL
Turn favorite workflows into one-tap modes.
Manage Workflow Studio from the SMSMobileAPI mobile app. Mark the workflows you use most as favorites, then activate or pause them directly from the app home screen—without opening the dashboard.
- 1
Create and test
Build the workflow in the dashboard or mobile app and validate it safely.
- 2
Add to favorites
Pin the workflows you want available the moment the app opens.
- 3
Switch with one tap
Activate or pause a favorite mode instantly from your mobile.
EXAMPLE MODES
A few useful modes to inspire you.
These are only examples. Create your own modes around your schedule, contacts, priorities and business needs, then add your most useful workflows to favorites for one-tap control from the mobile app.
Driving Mode
Acknowledge missed calls, notify the right person and delay non-urgent follow-up while you are on the road.
Focus Mode
Escalate only urgent messages while you code, create or concentrate without routine interruptions.
Family Mode
Pause professional automations outside work and keep only the essential alerts you choose.
On-call Mode
Route urgent messages and missed calls to the responsible person during a defined period.
Meeting Mode
Acknowledge missed calls during a meeting and forward only urgent messages to the colleague you choose.
Vacation Mode
Send an absence reply, route urgent requests and pause routine work notifications until you return.
WORKFLOW STUDIO API
Manage Workflow Studio directly through the API.
The Workflow Studio API lets your application list workflows, activate or pause them, manage mobile favorites and retrieve execution logs. Every change is synchronized with the dashboard and mobile app.
View the Workflow Studio API documentationGET/workflow/list/POST/workflow/state/POST/workflow/favorite/GET/workflow/logs/One visual logic: WHEN → SCHEDULE → IF → THEN.Each workflow starts with one event, can run only during the days, hours or date period you choose, evaluate up to 20 conditions, and queue up to 10 actions.+
TIME-AWARE AUTOMATION
Activate an automation only when it should be available.
A workflow is active all the time by default. When timing matters, use the same timezone as your profile and define exactly when the action is allowed to run. Events outside that schedule are safely skipped and remain explained in the execution log.
Always active
React to matching events at any time, without an availability restriction.
Every day
Choose one or more daily time windows, including a window that continues after midnight.
Selected weekdays
Use different availability windows for Monday, weekends, on-call days or any chosen day.
Fixed date period
Set an exact local start date and time and an exact end date and time for a campaign or temporary process.
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.
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.
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.
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.
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.
↗Explore visual examples from a simple missed-call reply to CRM, API and smart-office automations.
A REAL WORKFLOW AT SMSMobileAPI
Thomas, the CEO, connected a missed call to his office lighting.
Thomas defined a workflow for an important customer number and a precise availability period. If that customer calls during those hours and the call is missed, Workflow Studio sends the event to the office automation system through an HTTPS webhook. The office light then flashes immediately, so the missed call cannot go unnoticed.
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": "+12025550147",
"message": "urgent request"
}
}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.
Can I limit a workflow to certain hours or dates?+
Yes. Keep it always active, choose daily time windows, select weekdays with their own hours, or define an exact start and end date. The schedule follows the timezone configured in My Profile.
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.
