Agentled/mcp-server

Update non-secret channel configuration — enable/disable, default agent, allowed senders, outbound policy, etc. Allowed fields per channel: - email: enabled, allowedSenders (string[]), inboundAddress, allowOutboundEmail, allowedOutboundRecipients, requireOutboundApproval. defaultAgentId is legacy and ignored by email routing. - slack: enabled, defaultAgentId, defaultChannelId (Slack channel ID used to route inbound mentions when one Slack team is shared) - whatsapp: enabled, defaultAgentId - signal: enabled, defaultAgentId - telegram: enabled, defaultAgentId, botUsername, allowedChatIds Secr…

Configure the display-only Recent tab shown inside the existing workspace Home tab/table region, and choose which Home tab opens by default. Set config.defaultTabId to "recent" or to a use-case tab id listed by inspect_home_recent_tab to change the default tab; omit it to keep the legacy defaultSelected behavior. Requires the exact workspace revision returned by inspect_home_recent_tab and a full config object, or null to reset defaults. This only changes Home navigation and presentation: it does not run workflows, call providers, spend credits, change approvals, or mutate workflow/customer re…

Create a new agent with name, instructions, tools, workflows, and optional config files. The response includes channels for currently reachable inbound channels. Email is automatic per agent when the workspace email channel is enabled; use the returned email channel address rather than assigning a defaultAgentId for email. Agents are conversational AI Agents by default. For scheduled/autonomous work, create the agent first, then attach routines to it via create_routine (e.g. daily deal-sourcer, weekly digest). Key fields: - name: Agent display name - agentType: Preset template — 'personal-a…

Create a durable work handoff from a business agent to an external AI builder. Use sourceAgentEntityId to preserve the business-agent owner for review/email/UI.

Create a new knowledge list with a typed schema. Idempotent on key collision — returns the existing list with a warning instead of erroring, so AI agents can safely re-run setup steps. Use this before inserting rows to ensure the list schema exists. Returns: { listKey, fieldCount, kgSyncEnabled, alreadyExisted? }.

Create and enable a public form link for a workflow so anyone can submit the workflow input form without an account.

Create a new routine for an agent. Routines are paid autonomous features; free-tier workspaces cannot create or resume them. Interval values: By schedule: weekday-morning (Mon–Fri 08:00 UTC), weekday-evening (Mon–Fri 18:00 UTC), weekly-monday (Mon 08:00 UTC), weekly-tuesday-evening (Tue 18:00 UTC), weekly-friday-evening (Fri 18:00 UTC), daily (every day 08:00 UTC), monthly (1st of month 08:00 UTC) By interval: 6h, 48h Model format: "provider:modelId" e.g. "openai:gpt-5.4-mini" (default). Use skillIds from list_agent_skills for routine-level sk…

Create a manual config snapshot of a workflow's current state. Use this to save a checkpoint before making changes, so you can restore later if needed. Enforces plan-based limits (Pro=2, Teams=10, Custom=50). Returns an error with limit info if the snapshot limit is reached — delete old snapshots first to free up space.

Create a WorkspaceUseCase product record for a multi-workflow business goal. Use this before creating or attaching workflows for use cases such as sourcing, intake, front desk, or business intros. For config.useCasePage.body.columns, arbitrary badges can use case-insensitive valueRoles and numeric scores can use ordered minimum thresholds. Allowed semantic roles are neutral, accent, warning, success, and danger; never store CSS classes in config. This creates the product-layer object and linked references only; it does not create workflows, write KG rows, run providers, spend credits, trigger…

Create a new workflow. ## KG-First — before you write any prompt content If the workflow you're building contains workspace-specific content (investment thesis, ICP criteria, scoring rubrics, target sectors, brand voice, geo focus, seed lists), run this preflight before generating AI-step prompt strings: 1. **Inspect** — call `list_memories`, `list_knowledge_lists`, `get_knowledge_text` to see what already exists in the workspace KG. 2. **Seed** — if the content isn't in the KG yet, write it there first (`store_memory`, `upsert_knowledge_text`, `upsert_knowledge_rows`). Confirm with the use…

Create a workspace only when the caller has operator workspace-create scope; otherwise the request is rejected without mutation. Call resolve_workspace first. Trusted operators preparing a client workspace without changing plans, trials, or credits must set billingMode to planless. This setup primitive does not provision use-case kits, run workflows, insert candidate rows, send messages to customers, write CRM/calendar, call SignalKit receive, trigger routines, or spend provider credits.

Create a draft workspace skill backed by an existing AgentFile. The AgentFile content should contain the skill instructions/body. The WorkspaceSkill record stores lifecycle, risk, relevance, recommended apps/actions, and approval metadata. The allowedApps/allowedActions fields are recommendations for runtime guidance; actual availability still comes from the assigned agent app/action scope, runtime bundles, workspace connections, and approval gates. Prefer import_workspace_skill for Markdown/SKILL.md/JSON imports; use this low-level tool when you already have a reviewed AgentFile ID.

Create a saved WorkspaceView manifest over live workspace data. Workspace Views are general operating surfaces, not KG-only reports. Data sources can include KG lists/text, workflow executions/output pages/timelines, pending approvals, agent approvals, action queues, routine runs, external APIs, and custom sources. Creating the view writes only the manifest; it does not read sources, run workflows, insert KG rows, send messages, call providers, make approval decisions, or spend credits.

Permanently delete an agent and all its files. Attached routines are also removed by the API.

Permanently delete a file attached to an agent.

Delete a stopped workflow execution and its related timeline/chat records. EXCEPTION-ONLY admin maintenance tool. Requires an API key with admin:patch scope. Required operator flow: 1. Call stop_execution with a human-readable reason. 2. Wait until get_execution shows status "stopped". 3. Call delete_execution with reason and confirmExecutionId exactly matching executionId. The API rejects non-stopped executions and mismatched confirmation. This is destructive and should only be used for stopped test runs or incident cleanup.

Permanently delete a knowledge list and ALL its rows. This action is irreversible. Pass the listKey of the list to delete. The API requires confirm: true — this tool sends it automatically. Returns: { success, listKey }.

Delete specific rows from a knowledge list by their IDs. This action is irreversible. For more than 10 rows the API requires confirm: true — this tool sends it automatically. Returns: { deleted, errors[] } where each error includes a structured code field: - foreign_key_constraint: row is referenced by KG edges (scoring predictions, outcomes, relations) and cannot be hard-deleted - not_found: row ID does not exist - permission_denied: insufficient workspace permissions - delete_failed: unclassified failure IMPORTANT: Rows referenced by KG edges cannot be hard-deleted. If you receive f…

Delete a text-based knowledge entry by key. This action is irreversible. Returns: { success, key }.

Delete a specific memory by key.

Delete a public form link by token/id. Currently unsupported by External API (returns 501).

Permanently delete a routine. This cannot be undone.

Delete a specific config snapshot. Use list_snapshots to find snapshot IDs. Useful for freeing up space when the snapshot limit is reached.

Permanently delete a workflow by ID. This cannot be undone. **Two-phase flow (required):** 1. Call with just `workflowId` to get a deletion preview. Response: `{ pendingDelete: true, id, name, status, relatedEntities: { executions, leads, timelines }, relatedEntitiesTruncated, confirmToken, expiresIn: 300, expiresAt, message }` Nothing is deleted in phase 1. Token is valid for 5 minutes. 2. Call again with both `workflowId` AND `confirmToken` to perform the cascade delete. Response: `{ deleted: true, id }`. **Server error responses (always structured JSON):** - `404 { error: "Workfl…

Discard the draft snapshot for a live workflow. The live pipeline config stays unchanged. Use this to abandon draft changes and go back to the current live version.

Semantic intent router — describe what you want to accomplish in plain English and Agentled will find the best matching live workflow in your workspace. Optionally auto-executes the matched workflow. Examples: - "find the CEO's email for stripe.com" - "research acme corp and score them against our ICP" - "scrape https://example.com and summarize it" Returns the best match with confidence score, extracted inputs, and alternatives. Set execute=true to also start the matched workflow immediately.

Export a workflow as portable JSON for cross-environment transfer. Returns a self-contained WorkflowExport object with all steps, context, metadata, and pages. Workspace-specific identifiers (workspaceId, agentIds) are stripped so the export can be imported into any workspace. Use this together with import_workflow to move workflows between environments (e.g. sandbox → prod).

Get full details of an agent including its config, files, attached routines, and assigned inbound channels.

Get the content of a specific file attached to an agent.

Get detailed action schemas for a specific app. Returns input parameters, output fields, and credit costs. Use this to understand exactly what inputs an action needs when building workflow steps.

Get the workspace's whitelabel branding configuration. Returns the current branding settings: displayName, logoUrl, tagline, primaryColor, primaryColorDark, faviconUrl, and hideBadge. Use this to inspect the current client portal branding before making changes.

Get full builder work item context, outputs, activity, metadata, and review state.

Get the status or final result for a durable external chat turn returned by chat or chat_with_agent. Use this after a chat tool response returns status "running" and a turn_id. Polling this tool is idempotent and does not rerun the original prompt, model call, app actions, approvals, credits, or external sends.

Get the draft snapshot for a live workflow. When you update a live workflow, changes go to a draft instead of modifying the live pipeline. Use this to inspect the current draft state. Returns hasDraft: true/false and the draft config if it exists.

Get full execution details including results from each completed step. The executionContent field maps stepId -> step output data. Use this to inspect what a workflow produced, debug failures, or check intermediate results. executionId must be the PipelineExecution id, not executionInputId. If start_workflow returned only executionInputId, first call list_executions and match pipelineExecutionInputId to find the execution id. When sharing a step-specific run with a human, use /runs?runId=<executionId>&step=<workflowStepId>. Do not send a run-only URL and ask the human to open an approval/out…

Read the status and latest Agentled response for a submitted feedbackId in the current workspace. A null response means the team has not posted a reply yet.

Read and conservatively classify only the exact inbound body behind one already-correlated canonical IMAP replied tracking event. This is not a mailbox browser: the server derives the workspace, mailbox, and Message-ID from the canonical event, reads no attachments or remote content, enforces byte/message caps, suppresses no-reply follow-ups, and never sends a response. The external tool is read-only and does not persist the inspection.

Fetch rows from a knowledge list (paginated, up to 200 per call). Use this to inspect actual data or scan a small list end-to-end. Returns rows with their full rowData, count, totalCount for unfiltered list reads, and nextToken. Pass nextToken from the previous response to fetch the next page. nextToken is null when there are no more rows. When you mention this list back to a human, include the human-readable list name and stable list key when known, not only the key. For targeted lookups by ID use `get_knowledge_rows_by_ids` — it fetches specific rows in a single call (max 200) without scann…

Fetch specific knowledge rows by their IDs. Returns full row data for each requested ID (max 200 per call). Use this after `query_kg_edges` to load full row data for node IDs returned by the Knowledge Graph. The canonical chain for entity-scoped queries (e.g. "best deals for Teresa Abecasis") is: 1. `query_kg_edges({ entityName: "Teresa Abecasis", relationshipType: "SCORED" })` 2. `get_knowledge_rows_by_ids({ rowIds: <targetNodeIds from step 1> })` This is O(edges for that entity) — independent of total list size — and scales to 10k+ rows without paginating. Note: `source_node_id` and `…

Fetch a text-type knowledge entry by key. Use this to access text-based knowledge like feedback files, notes, or configuration text stored in the workspace. When you mention this text entry back to a human, include the human-readable title/name and stable text key. If no stored title exists, derive a short readable title from the key and still include the key. **KG-First:** Call this BEFORE generating any AI-step prompt that references workspace-specific content (investment thesis, brand voice, ICP description, scoring rubric, etc.) to check whether it already exists. If found, pass it via a …

Get one public form link by token/id.

Read one exact durable routine run and a bounded page of its ordered events. This is read-only and does not run, retry, resume, pause, approve, or send anything.

Fetch global scoring history for entities from the Knowledge Graph. Returns past scoring decisions (PROCEED_TO_IC, HOLD_FOR_REVIEW, REPOSITION, SCORED) with DMF scores and dates. Use this for manual exploration and legacy calibration. Workflow scoring prompts should prefer row-level scoring_profile fields or the kg.retrieve-scoring-memory app action when bounded target IDs are available. Returns both structured records and a compact text format for prompt injection.

Get share metadata by share id.

Read the full content of a config snapshot WITHOUT restoring it. Returns the captured `steps`, `context`, `name`, `description`, `goal`, `style`, and `analyticsConfig` under a `config` field, plus snapshot metadata (createdAt, source, label, updatedFields). Use this to inspect or compare an old snapshot against the live workflow without the destructive create + restore + restore dance. No quota cost.

Read a single step from a workflow by step ID. Cheap alternative to `get_workflow` (typically ~1KB vs 50-200KB for a full workflow). This returns the configured step definition only. To debug the actual prompt used in a specific execution, use `list_timelines` then `get_timeline` for that step invocation and inspect `metadata.computedPrompt`. **Use this before editing dictionary-shaped fields** (`stepInputData.fieldUpdates`, `responseStructure`, `knowledgeSync.fieldMapping`, `agent.workers`) when you need the current value for a complex local edit. For common single-key dictionary merges and…

Get allowed fields and minimal JSON examples for pipeline steps. Unknown fields are automatically stripped on save — only fields listed here are persisted. ## Params - `stepType` (optional): filter to one of `trigger`, `aiAction`, `aiActionWithTools`, `appAction`, `agentOrchestrator`, `code`, `knowledgeSync`, `share`, `return`, `milestone`, etc. Omit for the full schema. - `shape` (optional): minimal JSON example for a specific shape. Requires `stepType`. Examples: - `aiAction` shapes: `standard`, `report` (with Config renderer), `email` (composed email with approval). - `aiActionWithTo…

Get a single timeline (step execution record) by ID. Returns the full timeline including eventContent (step output), status, metadata, and context. Use this to inspect a specific step's result in detail. To debug the actual prompt used for this step invocation, inspect metadata.computedPrompt. get_step only shows the configured prompt template, not the resolved execution prompt.

Get one workspace use case by stored id, key, or workflowGraphId. Use this as the first inspection step for a specific business goal such as business-intro or front-desk. Read operatingGuides before answering workflow-specific questions or changing linked workflows. The normalized onboardingGoal field is stable desired configuration only; never infer live approval enforcement from it. If agentGuidance.warnings includes MISSING_USE_CASE_OPERATING_GUIDE, state that the operating README is missing and create/update the linked knowledge text before treating the context as complete. This tool is r…

Get the normalized onboarding-goal contract and freshly resolved approval enforcement for one WorkspaceUseCase. Use this instead of reading raw config when deciding whether an operation is automatic, approval-gated, disabled, misaligned, or unresolved. This tool is read-only and does not run workflows, trigger routines, call providers, spend credits, make approval decisions, or perform external writes.

Get the current fit assessment for one record in a workspace use case. The response keeps fit assessment separate from sourceOperationalStatus and explicitly reports zero workflow, routine, provider, approval, CRM, and credit side effects. This tool is read-only.

Get full details of a workflow including all steps, context, metadata, and configuration. Also returns hasDraftSnapshot (boolean) and draftSnapshot summary if a draft exists for a live workflow. When available, useCaseContext links the workflow to its WorkspaceUseCase and operating-guide README commands. Read the linked use case and guide before making workflow-specific claims or edits; missing-guide warnings mean context is incomplete.

Get aggregated workflow analytics from persisted snapshots. Use type="business" to retrieve business metrics configured in analyticsConfig, including trackingEvent metrics such as opened/clicked when configured. Use period="lifetime" for all-time totals or period="daily" for a time series.

Get ledger-derived, period-labelled credit usage for a single workflow. Defaults to period=rolling-30-days. Set includeCostDrivers=true for bounded step/model/app cost drivers. Always show the returned period.label/display/start/end with any credit total. Use all-time intentionally because it can scan more ledger rows.

Get workspace company info, current authenticated user, team visibility, and knowledge schema overview. Returns currentUser for the API key owner, company details, active team members when available, pending team invitations when available, and a summary of all knowledge lists with their field definitions and row counts. Use this as a first call to understand what data the workspace has.

Get the workspace company profile and company knowledge text. Returns the company record used for workspace setup plus markdown from knowledge keys company.profile and company.products. Use this when you need the editable company profile rather than the broader workspace context.

Get a concise, ledger-derived workspace credit cost-driver report. Defaults to period=rolling-30-days and includeCostDrivers=true. Returned totals are period-labelled; always show the period.label/display/start/end alongside credit totals. Cost drivers include bounded top workflows, steps, models, and apps. Use all-time intentionally because it can scan more ledger rows.

Get the authenticated workspace's canonical creditSnapshot plus optional period-labelled usage statistics. Returns: - creditSnapshot: schemaVersioned point-in-time balance (plan allowance, monthly remaining, purchased stored/available/unavailable, refresh/renewal dates, unsupported reservation=0, usable credits). Prefer these fields. - currentBalance / monthlyCredits / purchasedCredits / nextCreditResetAt: deprecated flat aliases during migration (monthlyCredits means remaining monthly balance, not plan allowance) - period: exact labelled window for every usage total (label, display, start, e…

Read the authoritative lifecycle and installation bindings for a registered workspace package. This is read-only and does not activate or run installed assets.

Get a workspace-created skill by ID.

Get one saved WorkspaceView by stored id or key. Read agentGuidance before rendering or acting from the view. View reads are safe; action execution must still use the normal approval and side-effect policies.

Create a new Agentled workflow from an n8n JSON import. Behavior: - runs deterministic import preview - creates workflow in preflight draft mode - stores imported contract for review/approval - does NOT auto-apply scaffold

Import a workflow from an export JSON into this workspace. Accepts the full WorkflowExport object (from export_workflow) and creates a new workflow with fresh IDs. Associated pages are recreated. Import provenance is recorded in the workflow metadata. Use this together with export_workflow to move workflows between environments. Tip: register separate MCP servers for sandbox and prod, export from one, import into the other.

Import a Markdown, SKILL.md, or JSON skill file into a draft workspace skill. This creates one backing workspace AgentFile and then one draft WorkspaceSkill. Imported allowedApps/allowedActions are recommended apps/actions only. Import does not grant those tools, publish the skill, assign it to an agent, run chat/routines/workflows, write providers, send messages, bypass approvals, or spend credits. Use publish_workspace_skill and explicit agent assignment only after reviewing the draft.

Inspect the workspace Home tabs and Recent tab configuration, and return the current workspace revision. Returns "tabs": every Home tab in display order (the Recent tab plus one tab per active use case) with its id, kind, label, and isDefault flag, plus "defaultTabId" for the tab Home opens by default. A Recent tab marked "visibleWhenRunsExist" has no stored configuration yet, so Home shows it only once the workspace has runs. Call this before configure_home_recent_tab. The configuration is display-only and inspecting it does not run workflows, call providers, spend credits, or mutate customer…

Inspect eligibility, installability, blockers, and current lifecycle state for a registered workspace package. This is read-only and reports every side-effect flag. It never installs, runs, activates, connects, calls providers, spends credits, sends, or imports data.

List all files attached to an agent. These include reference documents, knowledge files, and any other files uploaded to provide the agent with context.

List supported agent skill IDs for create_agent, update_agent, create_routine, and update_routine. Use these IDs in skillIds. They are stored internally as enabledSkills, but user-facing copy should say Skills. By default this returns only public user-facing skills. Pass includeRuntime: true only for advanced runtime bundle configuration such as workflow-operator, template-runner, inline-execution, routine-core, or channel-email. The agent-manager and routine-manager skills are control-plane tools for draft goal groups, owner agents, reusable assets, and paused schedules; activation or schedu…

List all agents in the workspace. Agents are workspace identities with instructions, files, assigned workflows, chat, and optional attached routines for scheduled/autonomous work. Each agent includes a channels array for currently reachable inbound channels: - email appears for every agent when the workspace email channel is enabled, with the derived per-agent address - Slack, WhatsApp, Signal, and Telegram appear only on the agent assigned as that channel's defaultAgentId

List available apps/integrations in Agentled. Returns app names, descriptions, and action summaries. Use this to discover what integrations are available before building a workflow. Common apps: agentled (LinkedIn enrichment, email finder), hunter (email), web-scraping, affinity-crm, specter, http-request. Pass `grep` to filter by keyword — much cheaper than fetching the full catalog when you only want to check a single platform (e.g. `grep: "producthunt"` to answer "is there a ProductHunt app?"). The keyword is matched (case-insensitive) against app id, name, description, and action ids/labe…

List work items eligible for this authenticated builder. Defaults to queued and needs_changes items assigned to the registered builder/API key when available.

List open/stale/submitted builder work items for a business agent by sourceAgentEntityId.

List the workspace's channel integrations and their configuration. Returns each configured channel (email, slack, whatsapp, signal, telegram) with: - enabled: whether the channel is active - defaultAgentId: the agent handling inbound conversations on default-routed channels - inboundAddress (email): workspace address pattern; each agent also exposes its own email in list_agents/get_agent/create_agent - Other non-secret config (team names, channel IDs, phone numbers) Secret credentials (bot tokens, access tokens, signing secrets) are REDACTED in the response. Use this to discover which channe…

List all connected integrations for the workspace. Returns a unified list of connections from all sources: - OAuth connections (via Composio) - API key connections (e.g., Hunter, Affinity CRM) with masked key preview - Native OAuth (social accounts) Each connection shows appId, status, source, and for API keys a masked keyPreview (e.g., "c5a1...5532"). Use this to check which apps are configured before running workflows that depend on them.

List recent executions for a workflow. Returns execution id, pipelineExecutionInputId, status, timestamps. Use pipelineExecutionInputId to match an executionInputId returned by start_workflow when executionId was not available yet.

List all knowledge list schemas with field definitions, row counts, and metadata. Returns detailed information about each list including fields, source type, category, entity config, and KG sync status. Use this to discover what lists exist and understand their structure before querying rows. When you mention knowledge lists or text entries back to a human, include both the human-readable name/title and stable key/id, not only the id. Example: VC Contacts (`gtm_vc_contacts`). **KG-First:** Call this BEFORE generating any AI-step prompt that references business-specific personalization (ICP cr…

List all memories in a given scope. Returns memories sorted by confidence.

List all supported AI models for workflow steps. Returns model ID, provider, display name, tier (mini/standard/max), credit cost, and category. Use the model ID in step.agent.model and the provider in step.agent.provider when configuring AI steps. Example: agent: { model: "claude-5-5-opus", provider: "anthropic" }

List output pages currently pinned to the workspace home/sidebar. Pinned outputs are workspace-level shortcuts to workflow output pages, stored on Workspace.metadata.pinnedOutputs. Use this before changing pins so you can avoid duplicating or removing the wrong shortcut.

List public form links for a workflow. Public URLs use /en/forms/{formLinkId}.

List all routines for an agent. Routines are scheduled tasks that run automatically on a fixed interval (e.g. daily, weekday-morning). Pass the agent's slug (e.g. "dealflow") or ID as `agent_id`.

List config snapshots for a workflow, paginated across all pages (cap 500). Snapshots are automatically captured before every external API update, allowing you to restore a previous configuration. Includes both saved versions and unpublished drafts. Use filter to narrow results: "all" (default, includes drafts), "saved" (no drafts), or "draft" (drafts only). Returns snapshot ID, timestamp, source, and which fields changed.

List timelines (step execution records) for a specific execution. Each timeline represents a step that ran, with its status, output, and metadata. Use this to inspect individual step results, debug failures, or see the execution flow. When sharing a specific timeline/approval/output/failure with a human, use /runs?runId=<executionId>&step=<workflowStepId>; the step value is the workflow step id from these records, not the timeline id. To debug the actual prompt used for a step in an execution, find that step's timeline here, then call get_timeline and inspect metadata.computedPrompt. get_step…

List raw tracking events for a workflow, such as email sent/opened/clicked events. Supports filtering by eventType, executionId, timelineId, channel, and createdAt range. Set aggregate=true to include simple counts by event type, channel, and URL for the returned page.

List current fit assessments for records in one workspace use case. Cleared/Unreviewed records are omitted. This tool is read-only and does not run workflows, trigger routines, call providers, change approvals, write CRM data, or spend credits.

List workspace use cases and their operating guides, linked workflows, agents, routines, AgentFiles, knowledge refs, data sources, config, validation, and metadata. Use this before building or changing a multi-workflow business goal so you can reuse the existing WorkspaceUseCase instead of hand-rolling disconnected workflows. Read operatingGuides/agentGuidance first; missing operating-guide warnings mean the agent context is incomplete. This tool is read-only and does not run workflows, spend credits, trigger routines, or write to providers.

List all workflows in the workspace. Returns compact workflow summaries plus small metadataSummary fields (analytics, workflowGraph, revision, imports, builder preflight state). Use get_workflow for full steps, context, raw metadata, full builder contract/compiler preview, and update history.

List workspace-created skills. These are draft/published/archived skill records backed by AgentFile content. Use import_workspace_skill for a one-step Markdown/SKILL.md/JSON import. Use create_workspace_skill only when you already have the backing AgentFile ID. Workspace skill allowedApps/allowedActions are recommended tools only; they do not grant app/action scope, runtime bundles, workspace connections, write access, or approval bypasses.

List saved workspace views and their source/action guidance. Use this before designing a new view so you can reuse or update an existing operating surface. This is read-only and does not run workflows, read provider data, mutate KG rows, make approval decisions, or spend credits.

Add, remove, or replace the workflows assigned to an agent without passing the full agent config. - operation 'add': append workflowIds to the existing list (no-op for IDs already present) - operation 'remove': remove specific workflowIds from the list - operation 'set': replace the entire list with the given workflowIds Use 'set' with an empty array to clear all assigned workflows.

Move a step to a new position in the workflow's steps array. Provide exactly one target: - `insertAfter`: place the step immediately after the given step ID. - `position: "first"`: place the step at index 0. Use this to put a trigger back in first position after a remove + add cycle (the only way to recover trigger order via MCP — `add_step` always appends at the end). - `position: "last"`: place the step at the end of the array. Only the array order changes — NO next pointers or step config are modified. This is a pure cosmetic reorder that fixes the "orchestrator-issue" validator warni…

Surgically edit a PipelineExecution's metadata, currentStepId, or status without re-running the workflow. EXCEPTION-ONLY tool. Primary use case: relabeling a stuck, completed, or test run's executionName so it's distinguishable in the executions list, without spending credits on a rerun. Other use cases: - Update metadata.debugNote during incident investigation - Update metadata.pendingReasonTag for UI annotation - Advance currentStepId for stuck-state recovery (only when status is waiting or failed) - Force status transitions: waiting/failed/credits_missing → running, or started → st…

Surgically edit a timeline's eventSummary, pending approval eventContent, or metadata fields without rerunning the upstream step. Terminal eventSummary-only relabels do not require confirmTimelineId; other terminal repairs require exact-ID confirmation. EXCEPTION-ONLY tool. Use cases: - Repair a malformed legacy/non-preview pending timeline that the regular approval editor cannot handle - Relabel a terminal timeline's eventSummary so the timeline row matches confirmed outcome, similar to metadata.executionName relabels on executions - Update metadata.pendingReasonTag for UI annotation …

Pause an active agent. Routines attached to the agent stop running until the agent is resumed via activate_agent.

Pause a routine (status → paused). The routine will not run until resumed.

Preview a deterministic n8n import from JSON. Returns: - normalized import hash and IR - mapped step graph - unsupported nodes + remediation - warnings/risks - draft workflow build contract and compiler readiness summary This is a read-only preview and does not create any workflow.

Preview the shared paused-package plan for a Source -> KG -> Process WorkspaceUseCase kit. Use this before creating multiple related workflows for sourcing, intake, monitoring, business intros, or other shared-tail use cases. The server compiles the typed kit into a workspace-local compatibility package and returns its exact signed preview. Review and preserve that preview for provision_use_case_kit. This is read-only: it does not create records, workflows, KG rows, sends, provider writes, routine runs, or spend credits.

Produce the exact signed, non-mutating install plan for a registered workspace package. Eligible existing assets can be reviewed with fingerprint-bound adopt or preserve resolutions. Adoption is additive: the existing identity and workspace-owned settings are preserved. Preview never applies or changes the workspace. The preview is bound to the workspace, designation, package version, manifest, authoritative snapshot, resolutions, operations, and approval reference. Review it before any apply.

Promote the draft snapshot to live. This overwrites the live pipeline config with the draft contents, then deletes the draft snapshot. A pre-promote snapshot is saved automatically so the previous live config can be restored if needed.

Deprecated compatibility alias for applying a previously reviewed Source -> KG -> Process WorkspaceUseCase package. Use preview_use_case_kit first, review the deterministic plan, and pass back its exact signed preview only after the user approves those writes. The server recompiles the typed kit and rejects any changed payload, stale preview, collision, or mismatched binding. This delegates to the shared paused package lifecycle; it does not run workflows, insert KG rows, send messages, write to external providers, trigger routines, make approval decisions, or spend credits. Requires confirmT…

Change the status of a workflow (publish, pause, or archive). Valid transitions: created/draft -> live, live -> paused, paused -> live, any -> archived. Use "live" to publish a draft workflow so it can be executed.

Publish a draft workspace-created skill.

Traverse Knowledge Graph edges by entity name and/or relationship type. Returns edges with source/target node IDs, relations, scores, and metadata. Use this to explore deal relationships, investor-startup connections, and scoring edges. Gracefully returns empty results if the Knowledge Graph is not configured. The `source_node_id` and `target_node_id` values correspond to knowledge row IDs. Use `get_knowledge_rows_by_ids` as the follow-up call to fetch full row data for those IDs. Example: `query_kg_edges({ entityName: "Teresa Abecasis", relationshipType: "SCORED" })` → collect `targetNodeIds…

Read the full output from a previous workflow step. Use this tool when a step output was deferred as a tool reference in a prompt — you will see a block like: [Tool Reference: stepName] Size: 24.3KB | Fields: name, emails, organizations, ... To read full data: call read_step_output(executionId="...", stepId="...") Pass the executionId and stepId shown in that block. Optionally narrow the response with 'field' (dot-notation path) or 'select' (list of top-level fields to include).

Recall a specific memory by key. Returns the stored value if found. Use this to retrieve previously stored facts, insights, preferences, or outcomes. **KG-First:** Call this BEFORE generating AI-step prompts that reference workspace-specific strategy (ICP, thesis, rubric). If the content exists as a memory, reference it at runtime via the workspace_memory builtin tool rather than pasting it into the prompt template.

Resume only the pending assets from an incomplete package installation using a fresh exact signed preview and confirmation. Recovery uses the same paused lifecycle and requires workspace:packages:apply plus workspace owner or ADMIN authority.

Terminally reject one pending AgentApprovalRequest in the current workspace. Requires the exact approval request ID, a non-empty operator comment, and confirm=true. This never approves, sends, executes, retries, continues, or invokes a provider. A prior terminal decision is preserved and cannot be overwritten.

Remove a step from a workflow with optional next-pointer rewiring. When rewireNext is true (default): steps that pointed to the removed step are rewired to the removed step's next target. Entry condition criteria referencing the removed step are also cleaned up. Respects draft snapshot routing for live workflows.

Remove one item from a step array path by `index` or exact `match` value. Provide exactly one of `index` or `match`. Prefer this over sending a hand-built shorter array via raw `update_step` when you only need to drop one entry. Returns the same shape as `update_step`.

Preferred for dictionary-shaped step fields where keys are user data. Merges the provided object keys into the existing dictionary at `path` without dropping sibling keys. Internally: `get_step` → merge → `update_step` with a safe top-level `replace`. Canonical paths: - `stepInputData.fieldUpdates` - `pipelineStepPrompt.responseStructure` - `knowledgeSync.fieldMapping` Use raw `update_step` only when you intentionally want a wholesale dictionary rewrite or a multi-path batch edit. Returns the same shape as `update_step` (merged step, diff, warnings, validation, draft metadata).

Set one nested step path to `value` while preserving sibling fields. Preferred for nested config edits such as `renderer.config.layout` where a naive `update_step` patch would wipe sibling config keys. Internally reads the step, clones the owning top-level field, applies the path write, then calls `update_step` with `replace` on that top-level field. For dictionary key merges (`fieldUpdates`, `responseStructure`, `fieldMapping`), prefer `replace_step_dictionary` instead. Returns the same shape as `update_step`.

Rerun or retry any step in a workflow execution. Pass the timelineId — the backend derives everything else (workflowId, executionId, stepId) automatically from the timeline record. Works for both retrying failed steps and rerunning any step regardless of status. Bypasses cache by default (forceWithoutCache: true). To find the timelineId: use list_timelines to browse step execution records for an execution, or get_execution which includes recent timeline IDs.

[Deprecated — use rerun instead] Rerun a specific step in a workflow execution, regardless of step status (pending, completed, failed, skipped). Works on any step and uses the current live pipeline config. Bypasses cache by default (forceWithoutCache: true). If no timelineId is provided, the most recent timeline for that step is automatically detected and rerun.

Check whether a workspace already exists for a firm, slug, domain, owner email, or idempotency key. This is read-only. Agents should call this before create_workspace so existing firm workspaces are reused instead of accidentally creating duplicates.

Restore rows from a snapshot into a Knowledge Data list without wiping computed fields. Modes (computed fields like scores and enrichment are always preserved): - "merge-restore" (default) — for rows that already exist: shallow-merges snapshot fields back in (existing computed fields survive; snapshot fields win on conflict). New rows are inserted. Use this as the rollback path — it undoes a bad migration without destroying downstream work. - "append" — inserts only rows not already present; never touches existing rows. Use this when restoring into a new list or when you want …

Restore a workflow to a previous config snapshot. Use list_snapshots first to find the snapshot ID. This will revert the workflow's steps, context, name, description, goal, and style to the state captured in the snapshot.

Resume a paused routine (status → active). Routines are paid autonomous features; free-tier workspaces cannot resume them. nextRunAt is reset to the next occurrence of the routine's interval from now.

[Deprecated — use rerun instead] Retry a failed step in a workflow execution. If no timelineId is provided, the most recent failed timeline is automatically detected and retried. This re-runs the failed step and continues the workflow from that point.

Review submitted builder work as a business agent; set accepted, needs_changes, or closed and optionally attach thumbs-up/down quality signal.

Revoke/delete share by share id.

Search memories by natural language query and/or category. Returns matching memories sorted by confidence. Use to find relevant stored knowledge. **KG-First:** Call this BEFORE generating AI-step prompts with business-specific content to check whether workspace strategy (ICP, thesis, rubric) is already stored. Reference found memories at runtime instead of inlining them in prompt strings.

Assign the agent that handles inbound conversations on a default-routed channel. Slack, WhatsApp, Signal, and Telegram use defaultAgentId routing. Email does not: email routes by per-agent address and agent responses include the derived address in their channels array. Use list_channels to inspect current assignments and list_agents to find valid agent IDs. Use configure_channel for more granular updates (enable/disable, allowedSenders, outbound email approval, etc.).

Update workspace-wide channel defaults (rate limits, timeouts, tool mode). These settings apply across all enabled channels: - maxSessionsPerDay: Cap on inbound chat sessions per day (default 100) - sessionTimeoutMinutes: Auto-close sessions after inactivity (default 60) - toolMode: 'all' (all tools available) or 'mcp' (MCP-only tools)

Pin or unpin a workflow output page on the workspace home/sidebar. The API validates that the workflow belongs to this workspace and that the output page pathname exists on the workflow. Pin sparingly: only use workspace-level pins for recurring reports, dashboards, canonical results lists, or other pages users should reach directly from the workspace home/sidebar.

Set the Knowledge Text key that contains the durable goal brief for one use case. This changes only the typed pointer. It does not edit Knowledge Text content, run workflows or routines, call providers, spend credits, decide approvals, or perform external writes. The server reuses the UI validator and writes an actor-attributed audit row.

Set the default finish line to one milestone already declared by the onboarding-goal contract. This changes desired goal configuration only. It cannot mutate runtime milestone evidence or mark work complete, and it does not run workflows, trigger routines, call providers, spend credits, make approval decisions, or perform external writes.

Set one typed desired approval policy on an existing onboarding-goal requirement. This changes desired policy only; it does not change live workflow, agent, channel, or routine enforcement and does not approve or execute any action. Weakening a send, write, or delete safeguard requires confirm=true. The server reuses the UI validator and writes an actor-attributed audit row.

Set the primary CRM reference used by one onboarding goal. This changes only the typed CRM reference. It does not connect the app, change credentials, write CRM data, run workflows or routines, call providers, spend credits, or decide approvals. The server reuses the UI validator and writes an actor-attributed audit row.

Set a Good fit, Not a fit, or Needs review assessment only after an explicit user instruction. This stores structured use-case memory for the exact record. It does not run workflows, trigger routines, call AI/providers, approve or reject pending work, write CRM data, mutate the source record, or spend credits. Free-form comments are untrusted evidence and are never promoted into prompts or scoring policy by this tool.

Create or get a share URL for an execution.

Capture a full point-in-time backup of a Knowledge Data list. Returns all rows with their IDs, rowData, status, createdAt, and updatedAt as inline JSON. Also includes the list schema (fields, userKeyField) so the snapshot is self-contained. Use before any risky migration, canonical-key reshuffle, or schema change. The returned snapshot object can be passed directly to `restore_knowledge_list_snapshot` to roll back. Supports lists up to 5 000 rows (inline JSON). Larger lists are not yet supported.

Start a workflow execution. Optionally provide input data that maps to the workflow's input page fields. For example, if the workflow expects "company_url", pass: { input: { company_url: "https://..." } } Returns executionInputId for the submitted input/run record. It may also return executionId when the async PipelineExecution row is already available. Use only executionId with get_execution/list_timelines/get_timeline. If executionId is absent, call list_executions and match pipelineExecutionInputId to the returned executionInputId; the matching row's id is the executionId. Mock control: b…

Stop an active workflow execution. Works on executions with status "running", "pending", or "started"; requires a human-readable reason persisted in execution metadata.

Store a persistent memory. Memories survive across workflow executions and can be recalled later. Categories: fact (known truth), insight (pattern/learning), preference (user preference), outcome (result to track). **KG-First:** Use this to seed workspace-specific strategy content (ICP criteria, scoring rubric definitions, investment thesis, brand voice) BEFORE building the workflow steps that need it. Once stored, the AI step references it at runtime via the workspace_memory builtin tool — never hardcoded in the prompt template.

Submit completed builder output refs and a summary. The work item moves to submitted for business-agent review.

Report a bug, request a feature, escalate an issue, or ask the Agentled team a question. Use this when you encounter something broken, have a suggestion for improvement, need human help from the Agentled team, or want to escalate a problem you cannot solve. Include a clear title and detailed description. Save the returned feedbackId and use get_feedback to read its status and the latest team response. The team can also reply by email: pass userEmail to choose where; if omitted, replies go to the email of the account that owns this API key.

Test an AI prompt in isolation without creating a workflow or execution. Pass a prompt template with {{variable}} syntax and variable values to run the AI and see the response. Useful for tuning prompts and response structures before adding an AI step to a workflow. Example: test_ai_action("Analyze this company: {{company}}", { company: "Stripe" }, { score: "number 0-100", summary: "string" })

Test an app action in isolation without creating a workflow or execution. Pass the appId and actionId (from list_apps / get_app_actions) plus input data to run the action directly and see results immediately. Useful for verifying inputs before wiring a step into a workflow. Example: test_app_action("web-scraping", "scrape", { url: "https://example.com" })

Test a code step in isolation without creating a workflow or execution. Pass JavaScript code with optional {{variable}} template syntax and variable values to execute in the same sandboxed vm context as the production orchestrator. Useful for verifying code logic and template variable resolution before adding a code step to a workflow. No credits consumed. Example: test_code_action("javascript", "const items = {{items}};\nreturn items.map(p => ({ name: p.fullName }));", { items: [{ fullName: "John" }, { fullName: "Jane" }] })

Run a routine immediately without changing its scheduled cadence. Free-tier workspaces cannot trigger routines. Use a short reason, for example "verify analytics monitor". Source must be one of: codex, claude, ui, api, mcp.

Description is built at runtime.

Remove one exact skill and agent reference from an onboarding goal. This changes goal configuration only. It does not remove the skill from the agent, revoke tools or app permissions, run providers, spend credits, or perform external writes. The server reuses the UI validator and writes an actor-attributed audit row.

Delete one step path. Thin wrapper around `update_step({ unset: [path] })`. Use for removing a stale input, config key, or leftover type-specific field after a shape change. The path must currently exist on the step. Returns the same shape as `update_step`.

Surgical update of one agent. **Preferred path for any single-field edit on an existing agent** — only the fields in `updates` / `replace` / `unset` are touched, every other field is left as-is. Same merge model as `update_step`. ## Merge semantics `update_agent` accepts three independent operations on the same call. At least one must be non-empty. - **`updates`** — partial agent patch. Top-level fields (`name`, `description`, `instructions`, `status`, `goals`, `chatModel`, `enabledApps`, etc.) are shallow-replaced. Nested objects (`configFiles`, `avatar`, `appPermissions`) are deep-merged …

Update a file that is already attached to an agent. Use this for durable reflection context such as JOURNAL.md, OBJECTIVES.md, and PEOPLE.md: read the current file first with get_agent_file, then send the full updated content. Update only when there is durable signal (decisions, corrections, objectives, people context, or useful learning), not for every chat turn. The file must already be linked to the agent, so this tool cannot accidentally edit an unrelated workspace file.

Update the workspace's whitelabel branding configuration. Set any combination of branding fields. Pass null or empty string to clear a field. Fields: - displayName: Brand name shown to clients (e.g., "Acme Corp") - logoUrl: URL to brand logo image - tagline: Short tagline under the brand name - primaryColor: Hex color for light mode (e.g., "#6366f1") - primaryColorDark: Hex color for dark mode (e.g., "#818cf8") - faviconUrl: URL to custom favicon - hideBadge: Boolean — hide the "Built with Agentled" badge (requires teams/enterprise plan)

Add or remove fields on an existing knowledge list schema. Use this to evolve a list's schema — add new columns or remove unused ones. Existing rows are not modified; new fields will be missing from old rows until updated. Returns: { listKey, fieldCount }.

Update a workflow public form link, including enabling/disabling it, limits, auto-share, expiry, and success message.

Update a routine's fields. Only provided fields are changed. If interval is updated, nextRunAt is automatically recalculated.

Update a single step by ID. Low-level merge primitive — prefer surgical tools for common single-path edits: - `replace_step_dictionary` — merge keys into `fieldUpdates` / `responseStructure` / `fieldMapping` without dropping siblings - `replace_step_path` — set one nested path while preserving siblings (e.g. `renderer.config.layout`) - `unset_step_path` — delete one path - `append_step_array_item` / `remove_step_array_item` — mutate `tools` / `integrations` safely Keep `update_step` for complex multi-path edits, shape conversions, and batch changes. Prefer it over `update_workflow` for any o…

Update a WorkspaceUseCase product record by stored id, key, or workflowGraphId. Use this to attach existing workflows, agents, routines, AgentFiles, KG refs, data sources, config, validation, owner, collaborators, or lifecycle status to the use-case hub. config.onboardingGoal.approvalRequirements is read-only through external tools and must be edited from Use case > Safeguards. For config.useCasePage.header, use source pointers rather than copied labels: workflow analytics require { source: "workflow-analytics", workflowId, metricId, window }, and channels require { channel, workflowId, stepI…

Update an existing workflow. ## Recommended flow for agent-driven edits For editing an existing workflow step-by-step, prefer the per-step tools — they catch errors incrementally and avoid the bulk-JSON vocabulary traps (`ai` / `integration` / `knowledge_graph_query`, silently-stripped root fields like `prompt` / `listKey` / `appId`): - `update_step({ workflowId, stepId, updates })` — change one step (prompt, inputs, next, etc.). Safest and most common. - `add_step({ workflowId, step, insertAfter? })` — append or insert a new step. - `remove_step({ workflowId, stepId })` — delete a step and…

Surgical edit of `workflow.context` (and `workflow.metadata`) — the workflow-level analog of `update_step`. Does NOT reach into `steps` (use `update_step` for that). ## Calling shape (preferred): three explicit verbs `{ updates, replace, unset }` — same merge model as `update_step`, but on **workflow-relative paths**. At least one must be non-empty. - **`updates`** — partial workflow patch. Top-level keys are limited to `context` and `metadata`. Each is shallow-merged (`{ ...stored, ...patch }`) so omitting a sibling preserves it. Direct sub-objects under `context` (e.g. `executionInputConf…

Update top-level workspace company profile fields. Use this for company identity and summary information such as name, industry, size, logo, website URLs, and company description. Products and services live in the company.products knowledge text, not in this structured profile.

Write the workspace-wide executive summary shown on the Workspace Assistant card. Uses the same summary signature as cluster executive summaries: body, optional bullets, and optional author. The API writes only Workspace.metadata.executiveSummary and preserves other workspace metadata keys.

Update a draft workspace-created skill. Published and archived workspace skills are immutable through this tool; archive and create a new version instead.

Update a saved WorkspaceView by id or key. This updates only the view manifest. It does not mutate source rows, execute view actions, start workflows, make approval decisions, call providers, or spend credits.

Upload a file to an agent. Files provide the agent with additional context such as reference documents, knowledge bases, or configuration data. - name: Filename (e.g. 'thesis.md', 'company-context.txt') - content: Raw text or markdown content (max 400KB) - mime_type: MIME type (default: 'text/plain', use 'text/markdown' for .md files) - role: Optional label describing the file's purpose (e.g. 'knowledge', 'context')

Create or update the external AI builder profile linked to this authenticated API key. Clients should call this after receiving a scoped API key; workspaceId and apiKeyId are derived server-side. Setup cadence for the builder: poll every 4h when idle/no active topic, every 1h when there is an active topic or recent assigned work, every 30m while work is in progress, and opportunistically call list_builder_work_items when already engaging with the user on another topic.

Create or update rows in a knowledge list. Maximum 500 rows per call — paginate for larger datasets. Resolution order per row: - rows with `id` → update existing row by id - rows with `userKey` → O(1) upsert (same userKey in the same list always maps to the same row, across calls and runs — ideal for idempotent sourcing/enrichment workflows) - rows with neither → plain insert with a fresh UUID (no dedup) Pick one stable key per row. `userKey` is caller-defined: a candidateId, a normalized URL, a domain, etc. Whatever string uniquely identifies the entity within the list for your use ca…

Create or update a text-based knowledge entry. Use this to store free-form text (notes, prompts, ICP descriptions, etc.) that can be retrieved by key. Returns: { key, upserted, created }.

Validate a workflow's pipeline definition. Returns structured errors per step. Use this after creating or updating a workflow to check for: - Missing step connections (broken next.stepId references) - Missing required fields (app action without inputs, AI step without prompt) - Unreachable steps (not connected to the trigger chain) - Invalid app/action IDs (not in the app registry) - Missing trigger or milestone steps - List field misconfigurations (missing itemFields, defaultValue format mismatches) - Config page field validation (missing name/type on input page fields) Each error/warning ma…

Verify whether a native OAuth connection is currently usable without executing an app action. Returns only a provider-neutral state, safe account label, and checkedAt timestamp. States are healthy, refresh-required, reconnect-required, missing-scope, provider-unavailable, or unsupported. API-key callers receive unsupported for user-owned native OAuth connections because their tokens remain available only to the authenticated Agentled workspace UI and authorized workflow runtime. Use list_connections to inspect safe connection metadata. Ask the user to verify from Workspace Settings > Integrati…