Monitor support activity
Poll conversation metadata to observe channel and status changes. Retain the last processed identifiers to prevent duplicate work.
Integrations Make
MakeHTTP workflow
MakeHTTP workflowYour workflow. Connected step by step.
Use Make HTTP tools with Message automation endpoints. Choose a supported event, map the fields and keep control of every action.
This uses generic HTTP tools, not a published native Message Make app or node. Platform usage charges and permissions are separate.
Automation
Make the connection useful.
- 01Message event
- 02Make workflow
- 03Your chosen action
React to AI task outcomes
Receive signed agent.completed or agent.failed webhooks and route the result to an internal workflow.
Run a configured task
A separately authorized automation:run key can enqueue an active Message task agent. Read-only keys cannot start work.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Read scope
Workspace identity, conversation routing metadata, active agents and task runs.
Run scope
Separate authorization is required to enqueue task-agent work.
Webhook topics
Task outcomes are supported. Do not assume chat messages or every conversation change have outbound webhook topics.
Your setup path
Start with one working flow.
- 01
Create scoped credentials
Open Message Automation settings. Use a read-only key unless your workflow needs to run a task.
- 02
Configure the HTTP workflow
Use Make HTTP tools and a server-side signature-verification step for webhooks. Configure the intended task or polling schedule.
- 03
Test retries and failures
Check a successful run, an invalid credential and a repeated event. Add deduplication and failure handling before enabling the workflow.