> 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/hootsuite/hootsuite/action-schedule-message.md).
# Action: Schedule Message
Hootsuite Operation
The Schedule Message action queues a social media post for future publication at a specified time.
{% embed url="" %}
#### Example User Story
I want to schedule a message to be posted on multiple social networks at a specific time so that I can plan my content calendar efficiently.
#### Fields
| Field Name | Field Type | Required |
| -------------- | ---------- | -------- |
| message | String | Yes |
| socialNetworks | String | Yes |
| scheduleTime | String | Yes |
| timezone | String | No |
### Related Connections
[Hootsuite](/hootsuite/hootsuite.md)
### Related Automations
Example link
### Code (Apache v2.0): Operation
```
{
"handle": "schedule-message",
"state": "inDev",
"meta": {
"short": "Schedule Message",
"description": "Schedule a message to be posted on social media platforms via Hootsuite."
},
"input": [
{
"name": "message",
"type": "String",
"required": true,
"meta": {
"description": "The content of the message to be scheduled."
}
},
{
"name": "socialNetworks",
"type": "String",
"required": true,
"meta": {
"description": "Comma-separated list of social networks to post the message (e.g., 'twitter,facebook')."
}
},
{
"name": "scheduleTime",
"type": "String",
"required": true,
"meta": {
"description": "The time to schedule the message in ISO 8601 format (e.g., '2026-03-18T12:00:00Z')."
}
},
{
"name": "timezone",
"type": "String",
"required": false,
"meta": {
"description": "The timezone for the scheduled time (e.g., 'America/New_York'). Defaults to UTC if not provided."
}
}
],
"output": [
{
"name": "messageId",
"type": "String",
"selector": ["id"],
"meta": {
"description": "The ID of the scheduled message."
}
},
{
"name": "status",
"type": "String",
"selector": ["status"],
"meta": {
"description": "The status of the scheduling request."
}
}
],
"steps": [
{
"type": "http",
"http": {
"method": "POST",
"path": "/messages",
"headers": {
"Content-Type": "application/json"
},
"bodyTemplate": {
"value": "{\"message\":{\"text\":\"{{message}}\",\"socialNetworks\":[\"{{socialNetworks}}\"],\"scheduledAt\":\"{{scheduleTime}}\",\"timezone\":\"{{timezone}}\"}}",
"placeholders": [
{
"name": "message",
"type": "String",
"description": "The content of the message to be scheduled.",
"required": true
},
{
"name": "socialNetworks",
"type": "String",
"description": "Comma-separated list of social networks to post the message.",
"required": true
},
{
"name": "scheduleTime",
"type": "String",
"description": "The time to schedule the message in ISO 8601 format.",
"required": true
},
{
"name": "timezone",
"type": "String",
"description": "The timezone for the scheduled time.",
"required": false
}
]
}
}
}
]
}
```
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.planetcrust.com/hootsuite/hootsuite/action-schedule-message.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.
