April 23, 2026

Taskade developer changelog — April 23, 2026: Generic Webhook Trigger (HTTP Piece) — GA, Mailhook Trigger — Now Free on All Plans.

Developer highlights. This section tracks API, MCP, SDK, automation, and Taskade Genesis platform changes for developers. For the full product changelog see taskade.com/changelog; for release newsletters see taskade.com/blog/updates.

What's New:

Generic Webhook Trigger (HTTP Piece) — GA

A new HTTP Webhook Received trigger is now available in the HTTP connector piece. It generates a unique inbound URL for each automation flow. Any POST request to that URL starts a flow run; the full request payload — headers, query parameters, and body — is available as output variables to downstream steps.

Key details:

• The trigger supports a live payload preview in the flow editor: after a test request is fired, the inspector panel shows the last received payload so you can map fields without running a full flow.

• Inbound webhook URL generation is handled on the automation backend; no external infrastructure is required.

• The generic webhook trigger is gated to Business plan and above (paywall enforced from April 24). Attempting to activate it on a lower plan shows an upgrade prompt.

• A test-trigger button is available in the flow editor to fire a synthetic payload and inspect the output mapping.

For automation configuration guidance see Actions & Triggers.

Mailhook Trigger — Now Free on All Plans

The Email Received (Mailhook) trigger, which starts an automation flow when a message arrives at a Taskade-hosted inbound email address, is now available on all plans — the previous Business-plan gate has been removed.

Each flow can be assigned a unique @mail.taskade.com address. Messages that arrive at that address trigger the flow with the sender, subject, and body as output variables.

Agent Context Includes Custom Fields

Agents that use the Retrieve Project Context tool now receive project custom fields in the tool output alongside tasks and notes. This means agents can reason about and act on structured metadata (assignees, priority, status dropdowns, date fields, etc.) without a separate lookup step.

This affects all agents using the Retrieve Project Context tool, including public agents and space agents.

See the comprehensive API guide for custom field schema details.

VFS + Bash Sandbox for Space Agents (shipped April 21)

Space Agents can now run inside the same VFS + Bash sandbox environment that was previously limited to EVE (the workspace-level AI agent). A space agent can read and write files in a virtual filesystem, execute bash commands, and mount project data for programmatic manipulation.

Key details for developers:

• The sandbox is gated by a feature flag per workspace and requires a plan that supports advanced agent capabilities.

• On-demand skill loading is activated for space agents: skills are fetched from the skill registry at agent creation time rather than bundled statically, allowing skills to be updated without redeploying.

See the Agents overview and the Automation README.