Communications · 42 pre-built actions
Twilio integration with Nexus
Reach people by SMS, WhatsApp and voice from a workflow. WhatsApp, SMS, voice and verification actions let workflows notify, confirm and verify people as recorded steps.
Pre-built actions
What you can automate
42 pre-built Twilio actions, grouped by what they work on.
42
PRE-BUILT ACTIONS
- 01SMS and WhatsApp actions send messages to people outside your tools.
- 02Voice actions place and manage calls.
- 03Verification actions confirm identity before a step continues.
Workflow
How it fits into a Nexus workflow
Twilio steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Twilio API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Verification before a change
A one-time code confirms the requester before a sensitive step runs.
Incident paging
A critical incident calls or messages the on-call engineer.
Customer notifications
Order or appointment updates go out by SMS or WhatsApp.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
FAQ
Twilio connector questions
- Which Twilio actions are pre-built?
- Nexus includes 42 pre-built Twilio actions across WhatsApp (10), Verification (7), SMS (8) and Voice (17).
- Can Twilio start a workflow?
- Runs that use Twilio start from a webhook, a schedule or another trigger source. Twilio steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Twilio API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Slack connector
Messages, users and channels.
- ServiceNow connector
Incidents, changes and CMDB.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Twilio fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.