> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/twilio/twilio/action-call-phone.md).
# Action: Call Phone
Twilio Operation
The Call phone action initiates an automated or custom voice call to a phone number using Twilio’s API.
{% embed url="" %}
#### Example User Story
I want to automatically call a customer via Twilio when their delivery is at the door, so they can confirm receipt instantly.
#### Fields
| Field Name | Field Type | Required |
| ---------- | ---------- | -------- |
| to | String | Yes |
| from | String | Yes |
| url | String | Yes |
| method | String | No |
### Related Connections
[Twilio](/twilio/twilio.md)
### Related Automations
Example link
### Code (Apache v2.0): Operation
```
{
"handle": "call-phone",
"state": "inDev",
"meta": {
"short": "Call Phone",
"description": "Initiates a phone call using Twilio's API."
},
"input": [
{
"name": "to",
"type": "String",
"required": true,
"meta": {
"description": "The phone number to call (E.164 format)."
}
},
{
"name": "from",
"type": "String",
"required": true,
"meta": {
"description": "The Twilio phone number to use as the caller ID (E.164 format)."
}
},
{
"name": "url",
"type": "String",
"required": true,
"meta": {
"description": "The URL Twilio will request when the call connects."
}
},
{
"name": "method",
"type": "String",
"required": false,
"meta": {
"description": "The HTTP method Twilio should use to request the URL (GET or POST).",
"default": "POST"
}
}
],
"output": [
{
"name": "callSid",
"type": "String",
"selector": ["sid"],
"meta": {
"description": "The unique identifier for the call."
}
},
{
"name": "status",
"type": "String",
"selector": ["status"],
"meta": {
"description": "The status of the call (e.g., 'queued', 'ringing', 'in-progress')."
}
}
],
"steps": [
{
"type": "http",
"http": {
"method": "POST",
"path": "/2010-04-01/Accounts/{{.AccountSID}}/Calls.json",
"headers": {
"Content-Type": "application/x-www-form-urlencoded"
},
"bodyTemplate": {
"value": "To={{.to}}&From={{.from}}&Url={{.url}}&Method={{.method}}",
"placeholders": [
{
"name": "to",
"type": "String",
"description": "The phone number to call.",
"required": true
},
{
"name": "from",
"type": "String",
"description": "The Twilio phone number to use as the caller ID.",
"required": true
},
{
"name": "url",
"type": "String",
"description": "The URL Twilio will request when the call connects.",
"required": true
},
{
"name": "method",
"type": "String",
"description": "The HTTP method Twilio should use.",
"required": false,
"default": "POST"
}
]
}
}
}
]
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.planetcrust.com/twilio/twilio/action-call-phone.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
