"Creating an Automation System Using n8n" matching MCP tools:

• automation_listA

  Perspective AIA

  Lists every automation configured on a perspective with its trigger, channel (sensitive details redacted), execution mode, enabled state, schedule description, and recent error/success metadata. Behavior: - Read-only. - Errors when the perspective is not found or you do not have access. - Sensitive parts of channel delivery (e.g., webhook auth headers, full URLs) are redacted before being returned. - has_error / last_error / last_error_at / failure_count appear only when there have been recent failures. When to use this tool: - Auditing what's wired up on a perspective before adding more automations. - Finding an automation_id to feed into automation_update, automation_delete, or automation_test. - Diagnosing a failing automation via last_error / failure_count. When NOT to use this tool: - Creating a new automation — use automation_create. - Toggling enabled or changing config — use automation_update. - Verifying delivery actually works — use automation_test.

  ConnectorOAuth

• word_createA

  Local MCPA

  Creates a new Word (.docx) document at `path` with the given text content (and an optional title rendered as the heading). Requires confirm=true — called without it, returns a preview of what will be written instead of creating the file. The path must be somewhere Local MCP can write; Desktop/Documents/Downloads may need a one-time Files-and-Folders grant (System Settings → Privacy & Security → Files and Folders). Returns {created, path}. For a OneDrive or Google Drive path use onedrive_write_file / gdrive_write_file; to append to an existing doc use word_append, to read one word_read.

  ConnectorOAuth

• submit_responseA

  Ansvar: EU Compliance & Legal IntelligenceA

  Provide an answer to the current step in a compliance workflow. Use this when someone provides information requested by the workflow, such as 'our system processes health data' or 'we use AES-256 encryption'. The workflow engine validates the response and advances to the next step. Pass user_acknowledged=true only after the user has supplied the fields listed in user_provided_fields. evidence_references accepts document UUIDs, doc:// segment URIs, or regulatory URLs. For an unattended gate, pass approved_by='auto' and leave user_acknowledged=false so the report does not misrepresent automation as human review. approved_by accepts only 'auto'; human review is asserted via user_acknowledged, never by naming an approver.

  ConnectorOAuth

• automation_createA

  Perspective AIA

  Creates an automation on a perspective. Triggers: per_interview (fires on every completed conversation) or scheduled (daily/weekly, with digest, invite, or insights purpose). Actions: internal insight discovery, webhook, email, or connected provider-backed integrations such as Slack, HubSpot, Gmail, Google Docs, Notion, and Confluence. Execution modes: direct (fast, deterministic, webhook-only) or agent (LLM-powered, required for insights and delivery channels). Behavior: - Each call creates a new automation — even if name/config matches an existing one. - Once enabled, the automation starts firing on real events: per_interview sends on every completed conversation going forward; scheduled sends a real message on the configured cadence (daily/weekly). - For HubSpot, the workspace's HubSpot connection is required — errors with "Could not resolve HubSpot portal ID — please reconnect HubSpot" if not connected. - Webhook channels: do NOT ask the user for the endpoint URL or credentials — neither is accepted through this tool. The automation is created disabled and the response includes configure_url, a web app page where the user sets the URL (and an authentication header if needed). Share that link and ask the user to reply "Done" after saving, then enable the automation via automation_update. - Insight automations use kind "insights", execution_mode "agent", omit channel, and use scheduled purpose "insights" when scheduled. - Errors when the perspective is not found or you do not have access. When to use this tool: - The user wants ongoing notifications on every completed conversation (per_interview). - Building a daily/weekly digest delivered to Slack, email, HubSpot, or a webhook (scheduled). - Running scheduled insight automation which creates insights without external delivery. When NOT to use this tool: - Trying a one-off send before going live — create the automation, then use automation_test (use override_email on email channels to avoid hitting real recipients). - Editing or toggling an existing automation — use automation_update. - Connecting Slack or HubSpot — use integration_manage first; the provider must be connected before slack/hubspot channels work. Example — per-conversation Slack notify (resolve the channel with slack_channel_resolve first, then pass it as resource_id): ``` { "perspective_id": "...", "automation": { "name": "Notify Slack", "trigger": { "type": "per_interview" }, "execution_mode": "agent", "channel": { "type": "composio", "delivery_config": { "provider": "slackbot", "tool_slug": "SLACKBOT_SEND_MESSAGE", "resource_id": "C0123ABCD", "resource_name": "#research" } } } } ``` resource_id is the Slack channel ID or name. The channel is re-verified live on create; an unresolvable channel is rejected. Typical flow: 1. integration_manage (operation: "list"/"connect") → ensure Slack / HubSpot is connected (only needed for those channels) 2. For Slack: slack_channel_search / slack_channel_resolve → find/verify the channel to use as resource_id 3. automation_create → create the automation 4. automation_test (with overrides) → verify delivery before relying on it

  ConnectorOAuth

• await_decisionA

  HatchA

  Create a human-in-the-loop review on the live artifact. Default options: Approve / Request changes / Reject. Reviewers see a Review required chip → modal. Request changes is non-terminal: webhook or poll returns changes_requested, then call continue_decision after regenerating. Optional timeoutSeconds and maxIterations (default 5). If the page has interactive controls (sliders/forms), the hatch HTML MUST expose window.__VR_HITL_GET_SETTINGS__ so the review can attach those assumptions as JSON. When the user integrates n8n, Temporal, CI, or any external workflow, pass webhookUrl (MCP opens the review; the platform POSTs each transition to that URL — prefer webhook over poll_decision for automation). See PARTNER-WEBHOOKS.md for event payloads.

  ConnectorNo auth

• create_webhook_endpointA

  Reach MCPA

  Register a URL to be called when something happens on LinkedIn, so an agent or an n8n/Make workflow can react instead of polling. Returns the signing secret ONCE; deliveries carry 'Reach-Signature: t=<unix>,v1=<hex HMAC-SHA256(secret, t + '.' + body)>'. Events: message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached, or '*' for all. Omit account_ids to subscribe for every account of the user. https only. Use when the user wants to react to a reply, a new connection, a quota alert or a job event from n8n, Make or their own code; needs an https URL they control. Not for the model to call itself.

  ConnectorAPI key

• 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

• list_missing_permissionsA

  Local MCPA

  Returns the macOS privacy (TCC) permissions Local MCP needs that are NOT granted yet, each with a one-click `open_url` that opens the exact System Settings → Privacy & Security pane. Read-only and passive (never prompts). Use it during setup or before a workflow to tell the user precisely which "Allow" clicks remain (Calendar, Contacts, Reminders, Automation for Mail/Messages/Notes/OmniFocus, Full Disk Access, Screen Recording, Accessibility) instead of failing mid-task. An installed app that is closed can't be checked and is listed under `unverified`. `all_granted: true` means nothing is left to do.

  ConnectorOAuth

• get_automationA

  MisarMail MCP ServerA

  Get one automation workflow in full: its trigger, every step with its settings, and current enrolment counts. Use it to understand exactly what an automation will do to contacts before activating it — the step list is where sends, waits and branches become visible. For the list of automations, use list_automations; to start or pause one, toggle_automation. Reads only; reading a workflow does not enrol anyone or trigger a step. Requires an API key. An automation can be defined but inactive, so check its state rather than assuming it is running.

  ConnectorNo auth

• create_opportunityA

  IndraftA

  Create an opportunity, always as a new one. If another system already knows this deal and you are syncing it, use upsert_opportunity, which matches on that system's identity instead of creating a second copy. Omit stageId to use the first open stage of the default pipeline. Amount is an integer in minor units and requires a currency. Set ownerActorId and expectedCloseDate here rather than in a second call: both are filterable and sortable, and recording one fact as two assertions makes the history harder to read than the API.

  ConnectorOAuth

• add_contactA

  mcpA

  Add someone to an audience. A contact exists once per workspace and can be on any number of audiences, so adding an address that already exists joins them to this list rather than creating a second copy. status records that the person opted out elsewhere — it writes the suppression as well as the flag, and an add never resubscribes someone who opted out here. Someone new to the audience starts any automation triggered by joining it; re-adding an existing member starts nothing. A retry has the same result. import_contacts adds up to 5,000 people in one call.

  ConnectorNo auth

• create_webhook_endpointA

  Reach MCP — LinkedIn for AI agentsA

  Register a URL to be called when something happens on LinkedIn, so an agent or an n8n/Make workflow can react instead of polling. Returns the signing secret ONCE; deliveries carry 'Reach-Signature: t=<unix>,v1=<hex HMAC-SHA256(secret, t + '.' + body)>'. Events: message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached, or '*' for all. Omit account_ids to subscribe for every account of the user. https only.

  ConnectorOAuth

• list_marketing_automation_listsA

  Metadata MCP ConnectorA

  List a Marketing-Automation provider's contact library lists — the selectable source for creating a Marketing-Automation-contacts audience. PREREQUISITE: • The provider MUST be connected. Only HUBSPOT and MARKETO expose library lists. WHEN TO USE: • Before create_marketing_automation_contacts_audience, to find the library_list_id. • "list my HubSpot lists", "which Marketo lists can I use for an audience". PARAMETERS: • provider (required): HUBSPOT or MARKETO. • list_type (optional): SMART_LIST | STATIC_LIST | ACTIVE_LIST. If omitted, the provider's own list types are queried and merged (HubSpot: STATIC_LIST + ACTIVE_LIST; Marketo: all three). • name (optional): filter by list name (partial). RETURNS: { lists: [ { library_list_id, name, status, listType, objectsCount } ] }. Use `library_list_id` for create. For HubSpot a list is usable only when status is DONE; for Marketo when READY.

  ConnectorAPI key

• ios_launch_app_in_languageA

  Robot Actions — Remote Device ControlA

  Launch an iOS app forced into a specific language / locale, without changing the device's system settings. Useful for QA testing app localization (e.g. open the app in Spanish without flipping the whole device to Spanish). Override is per-launch — relaunching the app outside this tool reverts to system language. Works whether or not an automation session is already open: it reuses an open automation session when there is one and launches the app directly when there is not, and says which path it used. The target app must use NSLocalizedString / Bundle.main.localizedStringForKey at runtime (modern apps do; some legacy apps cache locale on first cold launch — kill via ios_kill_app and re-call this tool to force re-read).

  ConnectorOAuth

• ios_rebootA

  Robot Actions — Remote Device ControlA

  Reboot an iOS device. DISRUPTIVE and NOT REVERSIBLE: the device is unreachable for roughly a minute, the automation session and the stream go down, and anything in progress on the device is lost. Requires confirm=true — there is no default. Do NOT reach for this to recover from a flaky tool call; try ios_end_session first, which resets the automation session without touching the device. Reboot only when the device itself is wedged and a human has asked for it. No automation session required. The Android counterpart is device_reboot.

  ConnectorOAuth

• list_destinationsA

  SignalRavenA

  List where your signals are delivered — Slack channels, webhooks, Google Sheets, n8n, Clay and Notion — with each destination’s health and recent failure state. Connection settings (URLs, tokens) are never returned.

  ConnectorOAuth

• create_automationA

  leadmarinaA

  Create an automation: re-run a search on a schedule and send the results somewhere automatically. Pass cities as plain strings (e.g. ['Austin, TX', 'Dallas, TX']) — they're resolved for you. IT SPENDS LEADS ON EVERY RUN, one per result, so confirm the niche, cities and cadence with the user before creating one. A destination of 'close', 'ghl' or 'google_sheets' requires that integration to be connected already (Close also needs one manual export first to save its field mapping); 'csv' | 'xlsx' | 'json' emails a file and needs nothing set up. Up to 20 automations, 25 cities each.

  ConnectorNo auth

• get_system_agentsA

  SpaceMoltB

  Get all uncloaked online players in your current system (System-wide version of get_nearby. Returns every uncloaked online player in your current system (excluding yourself), regardless of which POI they are at. Cloaked players are hidden, same visibility rules as get_nearby. Useful for cross-POI coordination. Returns an error if you are in hyperspace.)

  ConnectorNo auth

• ios_syslog_captureA

  Robot Actions — Remote Device ControlA

  Capture the iOS device's live system log for a few seconds and return the lines. This is the device log (os_log/syslog) — where crashes on launch, permission denials and app startup failures appear. Not app console logs: for a web page use ios_safari_console_logs. Filter with `process` and/or `contains` — an idle device produces hundreds of lines per second, so an unfiltered capture is mostly noise. Run the action you want to debug WHILE the capture is running, or capture right after it. No automation session required.

  ConnectorOAuth

• ios_navigate_urlA

  Robot Actions — Remote Device ControlA

  Navigate Safari to a URL on an iOS device via the automation session (address-bar type + submit), then VERIFY the navigation actually landed via the Web Inspector — so it never falsely reports success. For Safari, prefer ios_safari_navigate (CDP-based, also cold-opens Safari). Requires an active iOS automation session (auto-starts if needed).

  ConnectorOAuth

• ios_launch_appA

  Robot Actions — Remote Device ControlA

  Launch/activate an app on an iOS device by bundle ID. With no `arguments` it ACTIVATES — resuming the app in place and keeping its state — using the automation session when one is up and the direct device transport otherwise. Pass `arguments` to force a COLD relaunch with that argv instead (launch arguments are ignored on an already-running process, so the app is killed first). Arguments land in the process's argv, which is where NSUserDefaults reads its argument domain from, e.g. ["-AppleLanguages", "(fr)"] or your own debug flags; the override lives for that launch only.

  ConnectorOAuth