Overview
Most platforms have an "integrations page." Taskade has integrations everywhere. Memory imports the world. Intelligence calls the world. Execution runs through the world. Interface ships to the world. Four layers, one workspace, every door open.
TL;DR: Taskade integrates with external systems at every layer of Workspace DNA. Projects (Memory) import files and sync Google Calendar. AI Agents (Intelligence) call a built-in toolkit and your own services. The hosted Model Context Protocol (MCP) server is the other direction: it lets outside AI clients connect into your workspace. Automations (Execution) fire across 100+ connected apps and webhooks, and they are also the path that calls out to an external MCP server. Taskade Genesis Apps (Interface) publish to custom domains with built-in sign-in and shareable App Kits.
The four-layer integration map
Every external system connects to Taskade through one of four layers. Pick the layer that matches your job. The others wire up automatically.
Read it as a loop, not a stack. The world feeds Memory. Memory powers Intelligence. Intelligence drives Execution. Execution writes back to Memory and surfaces through the Interface. Every integration plugs into one node and inherits the loop.
Layer 1: Projects import the world
Projects are where outside information becomes Taskade-native records: searchable, agent-readable, automation-ready. This is the layer most people first reach for.
File uploads and text recognition
Drop any of these formats into a project, an agent's reference library, or Media Files and Taskade turns them into searchable Memory. Taskade also reads text out of scans and images for you, a step often called OCR:
| Format | Notes |
|---|---|
.md, .txt |
Plain text, native |
.docx |
Microsoft Word |
.pptx |
PowerPoint slide decks |
.xlsx, .csv |
Spreadsheets parse into table rows |
.epub |
E-books, chapter-aware |
.pdf |
Full text, plus text recognition for scanned pages |
| Images | Text recognition reads the words in the picture |
| YouTube links | Auto-transcribed |
| Webpages | Live scrape, refreshable |
Every file lands in the multi-layer search index. Agents read them by reference. Automations trigger on new uploads. Taskade Genesis apps can query them as live data sources.
Cloud-storage pickers
Inside the Agent Knowledge tab, the Add with picker pulls files directly from your existing storage:
- Google Drive
- Dropbox
- Box
- OneDrive
No re-upload. The link stays live. When the source updates, Taskade re-indexes.
See Agent Knowledge & Memory for the full picker flow.
Competitor importers
Migrating in? Taskade ships purpose-built import flows for 18+ tools:
- Project management: Notion, ClickUp, Monday, Asana, Trello, Todoist
- Notes & wikis: Obsidian, Roam, Logseq, Evernote, OneNote, Bear, iA Writer
- Outliners: Workflowy, Dynalist
- Whiteboards: Miro, Whimsical
- Docs: Google Docs
Each importer reads the source's own export file and uses AI to convert pages and databases into the right Taskade building blocks. See the full Import Guide for the supported sources.
Calendar feed and 2-way sync
Two calendar surfaces, different jobs:
| Surface | Direction | Providers | Plan |
|---|---|---|---|
| Calendar Feed | Read-only subscription link (iCal) | Apple, Google, Outlook | All plans |
| Calendar Sync | Two-way managed calendar | Google only | Paid workspaces |
The feed lets any standards-compliant calendar app subscribe to a Taskade workspace. The two-way sync creates a managed "Taskade" calendar in Google Calendar so events created on either side stay aligned.
Multi-layer search
Every Memory artifact is searchable through a single index that combines:
- Full-text keyword search across all project content
- Semantic similarity for "find something like this"
- Text recognition inside files so words in scanned PDFs and images count
- Permission-aware filtering so each searcher sees only what their workspace role allows
That last point is the moat. Search across competitors is either keyword-only or unaware of your team's permissions. Taskade does both layers in one query.
Layer 2: AI Agents call the world
Agents are the layer that acts on external systems. They connect through five distinct mechanisms.
Built-in tools
Every Taskade agent ships with a default toolbox. The most-used:
| Tool | What it does |
|---|---|
web.search |
Live web search with grounding |
website.extract |
Read a page's text content |
scrape.webpage |
Pull specific details out of a web page and return them as tidy fields |
transcribe.youtube |
Pull a transcript from any YouTube video |
image.generate |
Generate images with frontier models |
file.manager |
Read, write, and convert files |
taskade.* |
Manage projects, agents, automations, media inside the workspace |
bash |
Run a short script in a walled-off space that cannot touch anything else |
See Agent Tools for the full inventory of built-in tools.
Custom tools (your own services)
An API is the doorway a piece of software opens so other software can talk to it. If a service you use has one, an agent can call it. Agents define their own tools in three shapes:
- OpenAPI Action: Paste in the OpenAPI 3.x description file for any web service. Every operation in that file becomes a tool the agent can call, with its inputs checked first.
- Automation Action: Wrap any automation action as an agent tool. The agent picks when to call it. The action runs durably.
- Manual Trigger: Expose an automation trigger as a tool the agent can fire on demand.
The result: any service your company runs, any third-party app, any wrapped automation can become an agent capability without writing connecting code.
The hosted MCP server
The Model Context Protocol (MCP) is a shared standard that lets AI apps reach your tools. Taskade hosts an MCP server so outside AI apps (Claude Desktop, Cursor, VS Code) connect into your workspace. Sign in once and the app can browse and inspect your projects, read tasks, and edit Taskade Genesis app files.
Plan availability: The hosted MCP server is available on every paid plan, Starter and up. It does not run on the Free plan.
The opposite direction, MCP-as-Client, lets Taskade call out to an external MCP server (Notion, Linear, a custom server). It runs through automations with the MCP Client connector, on every plan. An agent still cannot reach a server on its own, so it hands the call to an automation.
Persistent Taskade EVE memory
Taskade EVE keeps workspace context in real Taskade Projects under projects/memory/. Account-wide preferences use a separate /user/PREFERENCES.md file. Edit or clear those preferences under Settings → Account. See Taskade EVE Memory for both kinds of memory.
Enterprise BYOK: bring your own keys (v6.163)
Bring your own OpenAI, Anthropic, and Google keys. Add them per space under Connections → AI Model Keys. Your agents and your Ask AI and Generate with AI automation steps then run against your provider contracts and billing. This applies whenever they name a specific model. Taskade no longer sits in the middle of the model call. You keep control of your own keys, sign data processing agreements directly with the provider, and get billing per space. See Bring Your Own AI Keys.
Plan-gated: BYOK is Enterprise-only on current plans. Some legacy lifetime and grandfathered plans also qualify.
Public agents with chosen tools
Embed an agent publicly with one link. The owner picks which tools and which internal integrations are exposed to anonymous visitors. See Public Agents.
Layer 3: Automations do the work
Automations are where Taskade does work in the outside world. Triggers in, actions out, 100+ integrations on call.
Connected apps and services
Automations reach five built-in step groups plus 100+ connected apps. The HTTP request action and Webhook Received trigger are your escape hatch for anything not yet on the list.
| Type | Examples |
|---|---|
| Connected apps | Slack, Stripe, Salesforce, GitHub, Notion, ClickUp, Microsoft Outlook, plus the general-purpose web request and webhook steps |
| Built-in step groups | Taskade, AI, Media, Schedule, Utilities |
Some connectors go deep. Google Drive, Gmail, Slack, and Notion each ship many triggers and actions. They cover file events, message delivery, and database updates end to end.
Browse the full catalog with live trigger and action counts at taskade.com/integrations.
Taskade triggers and actions
The taskade connector covers workspace events end to end, with triggers and actions for tasks, projects, comments, custom fields, and agents. It carries more surface area than any single SaaS connector:
| Triggers | Actions |
|---|---|
| Task Added | Create Project |
| Task Completed | Add Task |
| Task Assigned | Update Task |
| Task Moved | Move Task Within Project |
| Task Due | Assign Task / Unassign Task |
| New Due Date | Mark Task Completed / Uncomplete Task |
| Due Date Removed (v6.166) | Set / Clear Task Due Date |
| Task Custom Field Updated | Update Custom Fields |
| New Comment | Add Comment |
| Project Created (v6.166) | Set Project Title / Date Range |
| Project Completed | Tag / Untag / Pin / Unpin Project |
| Email Received (Mailhook) | Archive / Unarchive Project |
| Task Manual Trigger | Export Project / Get Project Info |
| Agent Public Chat Ended | Find Task(s), Run Automation, Notify by Email, Attach File, Convert Media, Create From Template, Send Agent Chat Message |
AI as an automation step
AI is a first-class action inside any automation:
Ask AI: a general AI call that can return tidy, labeled fields instead of a paragraph, in the JSON format other apps read (v6.162)Ask Agent: call any custom agent in your workspaceAsk Agent Team: fan out to multiple agents and aggregateCategorize AI: preset-based classification for routingGenerate AI/Respond AI: plain text generationRun Agent Command: invoke a specific agent skill
Media, utility, schedule steps
Beyond connectors, automations combine with built-in building blocks:
| Family | Highlights |
|---|---|
| Media | summarizeWebsite (v6.162), extractWebsiteContent, searchWeb, transcribeYoutubeVideo, convertPdfToText |
| Utils | jsonExtract (v6.161, pull one field out of JSON data by its path), formatDate, regex match/replace (find and replace by pattern), calculate, lookup, getField |
| Schedule | everyHour, everyDay, everyWeek, everyMonth |
| Control flow | Branch (if/else), Loop (for each), Filter (gate), Delay (wait) |
Web requests and webhooks (your own services)
Two escape hatches for anything not in the connector list:
- HTTP Request action: call any web service directly, with your own sign-in details and your own data in the request. Use it for internal tools, niche apps, or quick tests.
- Webhook Received trigger: a webhook is a private web address another system can ping when something happens. Taskade hosts a unique one for you. Any message sent to it starts the flow. You can protect it with a secret token.
Plan-gated: The Webhook Received trigger requires the Pro plan and above.
Durable execution
Every automation runs on a durable engine: failed steps retry automatically, work already finished survives a restart, and webhooks are never silently dropped. You write the flow once. Reliability is the platform's job.
Layer 4: Apps publish to the world
The Taskade Genesis App layer is where end users (strangers, customers, clients) touch your workspace. Seven first-class integration surfaces ship by default.
Custom domains with automatic SSL
Buy a domain through Taskade (.com, .org, .net, .app, .dev, .fyi) or bring your own by adding the CNAME and TXT records your domain provider asks for. Taskade handles the security certificate (SSL) and its renewal, the domain settings, page routing, and password gating end to end. See Custom Domains.
Plan-gated: Custom domains require Business plan and above.
GenesisAuth (v6.144+)
Drop-in email sign-in for any published Taskade Genesis app. Visitors sign in with their email right on your app's URL:
- No Taskade account needed for the people who use your app
- Secure, managed sessions you can revoke any time
- No sign-in server of your own to build or run
Short-lived sessions, rotated signing keys, no raw passwords ever stored. See GenesisAuth.
App Users (beta)
End-user management separate from your workspace team. Invite customers by email, tag them with roles you define, see every sign-in with provider and timestamp, revoke access in one click. App Users are not billed against your workspace seats. See App Users.
Personalize with currentUser
Once a user signs in, every layer of the app can read who they are through currentUser. Use it in agent prompts, automation filters, and project lookups to show each visitor their own view:
- "Only show the Billing page to users tagged
client." - "Show each signed-in user only their own row from the Projects database."
Taskade EVE wires these checks into the app from plain English. No conditional-logic code.
App Kits
Package a published app as a frozen bundle (Projects + Agents + Automations + the app interface) and share with a clone link. Recipients materialize the full Workspace DNA in their own workspace. See Community Kits.
Share an App Kit
Publish the kit to your profile or send the clone link. Anyone who clicks "Clone" installs the whole kit into their own workspace, subject to their plan limits per item.
Community Gallery and embeds
One-click publish to the Community Gallery. When a Taskade Genesis app is embedded in another page, the surrounding navigation strips out automatically, so embeds feel native to the host site.
Password-protected apps
Lighter alternative to per-user identity. Share one password with all visitors. Good for client portals and demos that do not need individual accounts.
Bring your own: the BYO ladder
Every layer has at least one "bring your own" escape hatch.
| Layer | Bring your own | Where to go |
|---|---|---|
| Projects | Files in any format, OCR-readable | Upload directly or via Agent Knowledge |
| Projects | Files from existing Drive / Dropbox / Box / OneDrive | "Add with" picker in Knowledge tab |
| Projects | Calendar events from Apple / Google / Outlook | Calendar Feed |
| Agents | Any web service as a tool | OpenAPI 3.x description file in agent settings |
| Agents | Your own AI app (Claude Desktop, Cursor, VS Code) | MCP Server (every paid plan) |
| Agents and automations | OpenAI / Anthropic / Google keys | Enterprise BYOK, under Connections |
| Automations | Any web address you can call | HTTP Request action |
| Automations | Inbound events from any system | Webhook Received trigger (Pro+) |
| Automations | Inbound email | Mailhook (unique address, all plans) |
| Taskade Genesis Apps | Built-in email sign-in for app users | GenesisAuth |
| Taskade Genesis Apps | Custom domain you already own | Custom Domains (Business+) |
| Taskade Genesis Apps | Public app page and clone link | App Kits |
The pattern: pick the layer that matches your job. Memory for bringing data in. Intelligence for agent capability. Execution for work that starts when an event happens. Interface for anything your customers see.
Plan-gating quick reference
Most integrations are available on every plan. A few are gated:
| Feature | Free | Starter | Pro | Business | Max | Enterprise |
|---|---|---|---|---|---|---|
| File imports | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Cloud-storage pickers | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Competitor importers | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Calendar Feed | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Calendar two-way Sync | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Built-in agent tools | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Custom OpenAPI tools (your own services) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Hosted MCP server | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Enterprise BYOK | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |
| Automation connectors | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| HTTP Request action | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Webhook Received trigger | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |
| Custom domains | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ |
| GenesisAuth | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| App Users | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| App Kit cloning | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Cross-layer examples
The best results come from one process that crosses multiple layers. Three concrete patterns.
1. Webhook to AI triage to Slack
A four-step flow that touches three layers:
HTTP Webhook (Execution) →
Ask AI structured output, JSON Schema (Execution + Intelligence) →
Create Task in correct project (Memory) →
Slack channel notification (Execution)
A vendor's system sends a message to your webhook address. Taskade EVE reads the incoming data and sorts it into a category. The sorted record lands in the right project. The team gets pinged in Slack. Durable execution means a failed Slack step retries without losing the record.
2. Client portal on your domain
A four-layer flow:
Project: client roster database (Memory) →
Agent: sales assistant with custom tools (Intelligence) →
Automation: weekly digest scheduled trigger (Execution) →
Taskade Genesis App: client portal at portal.acme.com (Interface)
Each layer plays its role. Projects hold the client roster. The agent answers questions about it. The automation sends a weekly status digest. The portal lets each client see only their own row via currentUser.email.
3. Share an app kit
A self-contained system:
Project templates (Memory) +
Agent presets (Intelligence) +
Automation flows (Execution) +
Taskade Genesis App UI (Interface)
→ packaged as an App Kit
→ shared with a clone link
→ the recipient's workspace materializes the whole DNA
You build a customer relationship management (CRM) system in a box. Recipients click "Clone" and the full Workspace DNA installs in their workspace. They get a working CRM on day one.
Related guides
- Workspace DNA. The four-layer architecture this article maps to.
- Agent Knowledge & Memory. How Projects feed Agent memory.
- Agent Tools. Full inventory of the built-in tools.
- Automations: The Execution Pillar. The canonical automations guide.
- Custom Domains. Brand your published Taskade Genesis app's URL.
- Watch: Connect Your Tools. A connection set up end to end, in under a minute.