Connect once, use in every task
Meerkat's Tools dashboard lists hundreds of integrations (Slack, Gmail, GitHub, Notion, Google Sheets, and more). Click Connect, authorize with OAuth, and you're done — no changes to the Task API.
When you submit a task that mentions Slack, Meerkat checks that Slack is connected. If not, you get a clear error with a link to the Tools page.
Example: DHL tracking → Slack
Example
curl -X POST https://cloud.meerkatagents.com/api/v1/tasks \
-H "Authorization: Bearer $MEERKAT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"task": {
"task_type": "recurring",
"description": "Fetch the DHL tracking page daily. When status changes, post an update to #shipping on Slack.",
"input_params": {
"courier_tracking_link": "https://www.dhl.de/..."
},
"frequency": "every 24 hours",
"output_webhook": "https://your-app.com/hook"
}
}'Slack approval flows
For human-in-the-loop workflows, describe approval in the task. Meerkat can post to Slack, read thread replies on later runs, and only push approved changes to your webhook — like a background teammate.
Example: price drop → Slack approval
Example
{
"task_type": "recurring",
"description": "Monitor competitor pricing hourly. When price drops more than 10%, post a Slack message to #pricing asking for approval. Read Slack replies on subsequent runs and only include approved changes in webhook findings.",
"frequency": "every 1 hour",
"input_params": { "url": "https://competitor.com/product" },
"output_webhook": "https://your-app.com/hook"
}Where to connect tools
- Meerkat Cloud: https://meerkatagents.com/docs/tools
- Self-host: same path on your Meerkat instance (/docs/tools)
- Requires COMPOSIO_API_KEY on the server