What Are Webhooks?
Webhooks allow Taskade to receive automated messages or data updates from other apps when certain events happen. In Taskade, for example, you can use webhooks to trigger actions like updating tasks or sending instant notifications using HTTP requests.
Set up Webhooks
The Webhook trigger allows you to configure the parameters of the incoming data. These parameters can be referenced in the subsequent actions in the automation. There is no limit to the number of parameters within a single trigger.
Navigate to the Automations tab at the top of your workspace.
Click ➕ Add automation ➡ Start from scratch.
Add a Webhook Trigger.
Configure the structure of the incoming data.
Add an Action to reference the configured parameters.
Take note of the unique Webhook URL shown in the trigger.
Activate the automation with the toggle in the top-right corner.
Here's an example of the structure of the received data and how it can be referenced:
And here's a data sample the Webhook trigger above can receive:
{
"Name": "John",
"Title": "CEO of Taskade"
}
Payload Parameters
To access nested values in your payload:
Select the JSON Object parameter in your webhook trigger.
Use the Add Field option select nested JSON properties.
Using Parameters
When setting up parameters in your webhook trigger (e.g. text, JSON object, email, or URL), you can reference them directly in your actions.
For instance, if your webhook receives a parameter named query with the value "my query", you can pass this value to an action by typing @ and selecting query. This ensures the action receives the exact value "my query".
Working with JSON Object Parameters
If your webhook includes a JSON object parameter, you can reference the full response by typing @ and selecting Webhook Body (Raw). This allows you to access the complete payload without defining individual parameters manually.
💡 Note: Passing the raw webhook body to an AI Agent action is particularly useful for extracting specific values or parsing structured outputs.
Trigger the Webhook
Sending an HTTP Request to Taskade
HTTP stands for HyperText Transfer Protocol. It’s a way for computers to communicate over the Internet. Think of an HTTP request like sending a letter to another app, and a Webhook is one way an application can receive this letter.
Using Make
Sign in to your Make account.
Click the Create a new scenario button on the top left corner of the screen.
Click the plus icon and choose HTTP from the available modules.
Select Make a request.
Fill in the URL field with the Webhook URL shown in the Taskade Trigger.
Select the Method as POST.
Select the Content type as JSON.
Input the data you want to send to Taskade in the Request Content input box.
Click on the Run Once button
💡 Note: The parameter name sent as the request content from Make must be exactly the same as the parameter name entered in Taskade's WebHook Trigger.
In this example, the received data will be added as a task to a project:
😊 Helpful Links
Download our apps: taskade.com/downloads
Leave feedback: taskade.com/feedback
Changelog: taskade.com/blog/updates
Watch tutorials: youtube.com/taskade
Contact us: taskade.com/contact
🤖 Taskade AI Essentials
Build with Taskade Genesis
Taskade Genesis lets you build complete apps, workflows, and dashboards from a single prompt — no code required. Describe what you need and Taskade Genesis creates a living system with connected projects, AI agents, and automations.
🧬 The Taskade Three Pillars
Your AI agents can learn from files, URLs, YouTube videos, and RSS feeds — and connect to external tools via 100+ integrations and MCP connectors.
🚀 Ready to Build?
Test Your Webhook
After setting up your webhook, test it by sending a request from your terminal. Here's how:
Basic test with cURL:
curl -X POST "YOUR_WEBHOOK_URL" \ -H "Content-Type: application/json" \ -d '{"name": "Test User", "email": "[email protected]", "message": "Hello from webhook!"}'
Replace YOUR_WEBHOOK_URL with the URL from your webhook trigger settings.
What to expect:
Success: HTTP 200 response — your automation will run
Invalid payload: HTTP 400 — check that your JSON matches the parameter names you defined
Webhook not found: HTTP 404 — verify the URL is correct and the automation is active
Common Integrations
Webhooks connect Taskade to virtually any tool that supports HTTP requests:
Tool | Use Case | How |
Zapier | Connect 5,000+ apps to Taskade | Use "Webhooks by Zapier" action → paste your Taskade webhook URL |
Make (Integromat) | Complex multi-step integrations | Use the HTTP module → POST to your webhook URL |
n8n | Self-hosted automation | Use the HTTP Request node → POST to your webhook URL |
GitHub | Trigger on push, PR, or issue events | Add webhook in repo Settings → Webhooks → paste URL |
Stripe | Payment and subscription events | Add endpoint in Stripe Dashboard → Webhooks → paste URL |
Troubleshooting
If your webhook isn't working, check these common issues:
Problem | Cause | Fix |
Automation doesn't run | Automation is paused or disabled | Toggle the automation On in the Automations tab |
Data doesn't appear in actions | Parameter names don't match | Ensure JSON keys exactly match the parameter names you defined |
Nested JSON not parsed | Parameter type set to "text" instead of "JSON object" | Change the parameter type to JSON Object and add sub-fields |
400 error response | Malformed JSON in request body | Validate your JSON at jsonlint.com before sending |
Webhook URL changed | Automation was deleted and recreated | Copy the new URL and update it in the sending tool |