"Inductive Automation" matching MCP tools:

• mcp_crm_automations_createA

  MailzzyA

  Create a new automation DEFINITION for the authenticated user. The new automation is always created INACTIVE (a definition only) — it does NOT run, send, or activate. Use when the user wants to define a new automation by name. Do NOT use to activate, run, or wire the automation's step graph — activation is a separate, later capability and is not available here. Do NOT use to edit an existing automation — use mcp_crm_automations_update. The automation's status cannot be set via this tool. Tenant is bound to the session and cannot be changed via arguments. Automation-level RULES (all optional, and all independent of the step graph — use mcp_crm_automations_set_steps for that): entryConditions / exitConditions / restartConditions are arrays of {type, segmentId, operator, contactFilters, campaignIds, linkUrl} where type is one of added_to_lists, removed_from_lists, contact_in_segment, contact_matches_filters, email_opened, email_clicked, email_unsubscribed; a membership type needs segmentId, contact_matches_filters needs contactFilters, and the email types take optional campaignIds (plus linkUrl on email_clicked). operator is MATCHES or DOES_NOT_MATCH. Pass an EMPTY array to clear a slot; omit the key to leave it unchanged. reentryPolicy is once (a contact runs this automation at most once) or every_time, with reentryWaitMinutes as the cool-down before a contact may re-enter. onDeactivate is continue (in-flight contacts finish) or cancel (in-flight contacts are cancelled when a human deactivates the automation). Returns the created automation projection (id, name, status, rules, version).

  ConnectorOAuth

• postkey_create_automationA

  Postkey: Instagram DM Automation and Comment-to-DMA

  Postkey: Builds a new DRAFT Instagram DM automation from a template and returns its automation_id, for example comment-to-DM: send a link by DM when someone comments a keyword. It is made the same way as on Postkey's New automation screen. Use it for a new automation; to change one that exists use postkey_update_automation. It is not switched on: nobody gets a message until postkey_publish_automation (preview that first). Pass keyword and link_url when the template's needs_keyword or needs_link is true. The answer says back runs_on and followers_only (follow_note when follow-gated). Refused before anything is made: an X account or one not connected for DMs (invalid_arguments), and a follow-gated automation on a Facebook Page (not_on_this_network).

  ConnectorOAuth

• pm_list_reference_dataA

  DutifyB

  List a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.

  ConnectorNo auth

• pm_list_reference_dataA

  DutifyA

  List a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.

  ConnectorNo auth

• run-automation-toolA

  0bull Phone FarmA

  Start one of the user's automations now, the same as "Run now" in the web app. The AI agent then drives the automation's phones on its own; this returns the run at once with status "queued". Poll get-automation-run-tool with its `id` until `status` is done, failed or stopped, then read `outcome`, `result` and `phone_reports`. A run can be refused (the automation is off, a run is already going, the daily limit is reached, no phone is online, or the agent is unavailable); the error says which. A `tiktok_warmup` automation (see list-automations-tool) has no daily limit and starts one session per phone at once, so this returns the first one already "running" alongside `sessions`, the number started, and `skipped_busy_slots`, the phones left alone because another run already drives them; `payload` is ignored, it has no parameters.

  Connector

  Destructive

  OAuth

• postkey_list_automationsA

  Postkey: Instagram DM Automation and Comment-to-DMA

  Postkey: Lists the profile's DM automations (for example "comment GUIDE, get the link by DM") one page at a time (next_cursor; null: the last page): id, name, status (draft, live, paused, error), made_with (Quick form, Flow Builder, or Postkey (a built-in automation)), unpublished changes, and what starts each one with its keywords. Without search, newest edits first. With search, names AND keywords are matched, each result with match: "keyword" (a keyword is exactly the search), "name" (a whole word of its name) or "partial". When some automation has the search as a keyword, only those are listed unless include_partial is true. For a keyword ("the LIST automation"), act only on results with match "keyword": "name" and "partial" are other automations. match_note says which to act on. Use it to find an automation id; use postkey_get_automation for one automation's messages and settings, postkey_get_automation_stats for results, and postkey_list_automation_templates to make a new one.

  ConnectorOAuth

• automation_deleteA

  Perspective AIA

  Permanently deletes an automation. Pauses any scheduled sends first, then removes the automation. Behavior: - DESTRUCTIVE and irreversible — the automation cannot be recovered. No undo. - Errors when the perspective or automation is not found, or you do not have access. Deleting an already-deleted automation errors as well. - If pausing the scheduled sender fails, the deletion is aborted and you'll get success: false with "Failed to stop running workflow. Please try again." — the automation stays intact in that case. When to use this tool: - The user explicitly asked to remove an automation and confirmed. - Cleaning up a misconfigured automation that automation_test repeatedly fails on. When NOT to use this tool: - The user just wants to pause it temporarily — use automation_update with { enabled: false } instead. - You're not sure which automation_id is correct — confirm via automation_list first.

  Connector

  Destructive

  OAuth

• update_automationA

  OmniSocialsA

  Change a comment-to-DM automation: pause or resume it (status), new keywords or match, a new DM text or public replies, new limits, or move it to another post (post_id, instagram_media_id or facebook_post_id). Only the fields you pass change. The platform cannot change: to move to another channel (Instagram, the Facebook Page or X), create a new automation. Turning an X automation on (status 'active') needs X DMs on for the workspace, else 409 x_dms_off. A 'completed' automation starts again when its limits or trigger change.

  ConnectorOAuth

• read_guidesA

  Arcadia FinanceA

  Get Arcadia workflow guides and reference documentation. Call this before multi-step workflows (opening LP positions, enabling automation, closing positions) or when you need contract addresses, asset manager addresses, or strategy parameters. Topics: overview (addresses + tool catalog), automation (intent-based automation setup), strategies (step-by-step templates), selection (how to evaluate and parameterize strategies).

  ConnectorNo auth

• list-automations-toolA

  0bull Phone FarmA

  List the authenticated user's automations. An automation is a saved task for the AI phone agent (`prompt`) that runs across one or more phones, on a schedule (`schedule_cron` in `timezone`), when its webhook is called, or on demand with run-automation-tool. Each run is followed with list-automation-runs-tool and get-automation-run-tool. `kind` is "prompt" for that, or "tiktok_warmup" for a TikTok account warm-up: its `settings` (niche, keywords, comment language, daily window, session counts and lengths) replace `prompt` and it has no `schedule_cron` — it plans and runs its own sessions every day on its own timetable, and run-automation-tool only ever starts an extra one now. Not the same as macros (list-macros-tool), which replay recorded input exactly with no AI. Automations are created and edited in the web app.

  ConnectorOAuth

• setUpModuleA

  Duvo MCPB

  Set up a Duvo Module (a ready-made solution such as AP Invoice Intake & Routing or Freight Audit) as a new Automation on the team, the same as pressing Set up on the Module in the web app. Creates the Module's Agents, code steps, Queues, Policy and dashboards in one call. If the team already has a demo of this Module open, the call is refused with 409 unless `convert_existing_demo` is true; then that demo becomes the Automation and its sample cases and Runs are deleted, so ask the user first. The Automation starts in setup and does not run yet: call `getAutomationReadiness` next to see what is left of the setup, the Policy questions, the current process and the automation proposal, whose approval builds the automation. Connections and routing come once the approved proposal is being built, so don't raise them before. Give the user the `url`.

  Connector

  Destructive

  No auth

• updateAutomationA

  NextmailA

  Change an automation. Its name, description and settings apply at once. definition replaces the whole draft, so start from getAutomation, change the JSON and pass all of it back. A live automation keeps running its published version until publishAutomation, and contacts already in it stay on the version they entered on. Pass only what changes.

  Connector

  Destructive

  OAuth

• list-automation-executionsA

  Apdf — PDF Tracking & AnalyticsA

  List all automation executions. Each entry includes the matched event, the payload sent and the endpoint response. Supports paging via "page" and "per_page".

  ConnectorOAuth

• delete-automationA

  Apdf — PDF Tracking & AnalyticsA

  Delete an automation and its execution history. To keep the rule and only stop it from firing, use "deactivate-automation".

  Connector

  Destructive

  OAuth

• automations_send_testA

  Mailrith Email MarketingA

  Sends up to five selected saved Automation email steps to one explicit test address. This does not start the Automation or run other actions. Effect: external-email. Retry with the same idempotency_key. Permissions: live_actions:write, subscribers:read, automations:write. API reference: https://mailrith.com/developers/api-reference.

  Connector

  Destructive

  No auth

• update_automationA

  leadmarinaA

  Pause an automation (active=false) so it stops running and stops spending leads, or resume it (active=true). Pausing is the safe way to stop an automation you might want back — use delete_automation only when the user wants it gone for good.

  ConnectorNo auth

• set_default_ma_listA

  Metadata MCP ConnectorC

  Set the account’s default marketing-automation destination list by a resolved list_id from search_ma_lists. The default affects newly created campaign channels; existing channels retain their captured values. Returns the updated setting or a failure such as PERMISSION_DENIED or DISCONNECTED. Account marketing-automation write access is required.

  ConnectorAPI key

• list_automation_runsA

  CourierB

  List automation runs, newest first. Filter by automation template, status, or a created_at window to find a run that stalled or errored, then read its steps with list_automation_run_steps. Journey runs are listed by list_journey_runs instead.

  ConnectorNo auth

• getSessionScreenshotsA

  MCP Server By TestMu AIB

  Retrieve command-by-command screenshots captured during a test session. Returns screenshot URLs for each step. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.

  ConnectorOAuth

• getSessionVideoA

  MCP Server By TestMu AIB

  Retrieve the video recording URL for a completed test session. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.

  ConnectorOAuth

• getSessionScreenshotsA

  TestMu AI (formerly LambdaTest)B

  Retrieve command-by-command screenshots captured during a test session. Returns screenshot URLs for each step. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.

  ConnectorOAuth