Add Missing AI Agent + Automation Actions and Triggers for Zapier, Make.com, n8n, and Beyond

Start by reviewing the attached taskade-actions-triggers-schema.json and the listed Taskade API endpoints. Then determine how the repository represents actions and triggers before mapping the requested agent, automation, folder, task, and form events. Done means the agreed capabilities are implemented, categorized, and represented in the portable schema for the named integration platforms.

To expand our Zapier and portable integration coverage (Zapier, Make.com, n8n, etc), we need to expose more of Taskade's AI Agents, Automations, and Agentic Workflows as Actions and Triggers. This will improve workflow flexibility, deepen platform integration, and strengthen Taskade's product moat.

---

✅ Goals

• Support AI Agent lifecycle and knowledge injection via Actions

• Support automation and conversation-based Triggers

• Enable real-time flows via webhook-ready architecture

• Group actions and triggers into categories for long-term reuse and documentation

• Convert to portable schema format (JSON, TypeScript scaffolding)

---

🧠 AI Agent Actions (High-Moat Features)

• Create AI Agent
  POST /folders/{folderId}/agents
  Spawn new agents dynamically during workflows

• Update AI Agent
  PATCH /agents/{agentId}
  Modify agent commands, tone, name, etc mid-workflow

• Add Knowledge to Agent (Project/Media)
  POST /agents/{agentId}/knowledge/project
POST /agents/{agentId}/knowledge/media
  Feed dynamic knowledge into agents for personalized context

• Enable Public Access to Agent
  PUT /agents/{agentId}/publicAccess
  Make agents public as part of an automation flow

---

🤖 Automation & Agent Triggers

• Agent Conversation Started / Responded
  GET /agents/{agentId}/convos/
  Trigger follow-up workflows based on conversation state

• Agent Generated Project
  (Trigger based on AI agent execution result logs)

---

📂 Folder/Workspace-Level Triggers

• New Project in Folder
  GET /folders/{folderId}/projects
  Useful for provisioning workflows and client onboarding

• New Agent in Folder
  GET /folders/{folderId}/agents
  For auditing, monitoring, or deployment pipelines

---

✅ Task-Level Triggers (Improvements)

• Task Marked Complete by Agent
  Track who/what marked task complete --- trigger downstream reviews or summaries

• Task Updated
  Trigger when the following change:

  • Note added/updated

  • Due date set

  • Assignment changes

---

🧪 Internal Automation Triggers

• Automation Executed / Succeeded / Failed
  New internal trigger (or webhook event) for when a Taskade Automation finishes
  Enables:

  • Meta automations

  • System monitoring

  • Logging to Slack, Notion, etc

---

🧰 AI Form Trigger

• Form Submitted (AI Form Trigger)
  Trigger when user submits a public AI Form
  → Use cases: intake forms, lead capture, onboarding flows

---

🔧 Future-Proofing Suggestions

• Add support for webhook-based triggers
  → Removes polling
  → Enables real-time automations across platforms

• Map every POST, PUT, PATCH, DELETE = Action

• Map every GET or pollable endpoint = Trigger

• Group into categories:

  • Project Automation

  • Agent Management

  • Knowledge Management

  • Forms & Events

  • System-Level Events

---

📦 Bonus

We’ve started mapping this into a reusable schema format:
taskade-actions-triggers-schema.json (portable for Zapier, Make, n8n, etc)

taskade-actions-triggers-schema.json