Skip to main content
Glama
650,225 tools. Updated 2026-10-12 23:53

"Creating workflows in N8N automation platform" matching MCP tools:

  • Upload images directly to Metadata platform library to create image creatives. Downloads images from provided URLs and uploads them to the platform. REQUIRED STEP IN AD CREATION WORKFLOW: This tool MUST be called between generate_brand_creative and create_update_image_ad. **WORKFLOW INTEGRATION:** This tool is part of the ad creation workflow and should be used: 1. BEFORE creating ads with create_update_image_ad (which requires imageLibraryId/creativeID) 2. IN COMBINATION with generate_brand_creative to create AI-generated images first, then upload them 3. When you need to upload existing images from external sources **COMMON WORKFLOWS:** - Upload existing images → Get imageLibraryId → Use in create_update_image_ad - Generate image with generate_brand_creative → Download generated image → Upload with this tool → Use in create_update_image_ad - Batch upload multiple creative assets for campaign preparation **IMPORTANT:** The returned image ID (imageLibraryId/creativeID) is REQUIRED when creating ads. Every ad needs a creative asset, so you must upload images first before calling create_update_image_ad. REQUIRED PARAMETERS: - images: Array of image URLs to upload IMAGE REQUIREMENTS: - URLs must be valid and publicly accessible - Supported formats: PNG, JPG, JPEG, GIF, WebP, and others - Images will be downloaded and then uploaded to platform - Filenames with spaces will have spaces replaced with underscores EXAMPLES: Single Image: upload_image([ "https://my-bucket.s3.amazonaws.com/images/sample-image.png" ]) Multiple Images: upload_image([ "https://my-bucket.s3.amazonaws.com/images/logo.png", "https://example-assets.s3.us-west-2.amazonaws.com/photos/banner.jpg", "https://content-bucket.s3.eu-west-1.amazonaws.com/uploads/hero image.webp" ]) RESPONSE FORMAT: Returns array of objects for each image: [ { "url": "https://original-url.com/image.png", "name": "image.png", "id": 12345, "success": true }, { "url": "https://failed-url.com/bad.png", "name": "bad.png", "id": null, "success": false, "error": "Download failed: Connection timeout" } ] ERROR HANDLING: - If one upload fails, others will continue - Each result includes success status - Failed uploads include error message - Successful uploads include platform image ID USE CASES: - Upload creative assets before creating ads - Import images from external sources - Batch upload multiple campaign images - Migrate images from other platforms
    ConnectorAPI key
  • Create a Marketing-Automation-contacts custom audience (platform customAudienceType MA_CONTACTS_STATIC or MA_CONTACTS_DYNAMIC) from a provider library list. This is one of the audience types eligible for Microsoft Ads (Customer Match). Use it when a user wants a Marketing-Automation-sourced contacts audience, including for a Microsoft Ads campaign. PREREQUISITE: • The provider (HUBSPOT or MARKETO) MUST be connected — the platform validates this and returns a clear error if not. • A library_list_id from list_marketing_automation_lists — do NOT invent one. For HubSpot the list must be DONE; for Marketo READY. VARIANT (mirrors the UI's static/dynamic choice): • STATIC → MA_CONTACTS_STATIC — snapshot at creation, does not refresh. • DYNAMIC → MA_CONTACTS_DYNAMIC — refreshes as the provider data changes. • If the user did not say which, ASK — do NOT default and do NOT infer it from the source list's type. A HubSpot STATIC_LIST is not the same choice as a STATIC (snapshot) audience; the audience variant is the user's call, independent of the list's type. ASYNC: the platform creates the audience in the background and returns a flow id, NOT a ready audience id. The audience appears under the account's Marketing-Automation audiences once the flow completes, and its contact count fills in then. Do not expect to associate it to a campaign in the same turn. PARAMETERS: • custom_audience_name (required): the audience display name — must NOT contain '/'. • library_list_id (required): id from list_marketing_automation_lists. • provider (required): HUBSPOT or MARKETO. • variant (required): STATIC or DYNAMIC. • list_name (optional): the source list's own name (from the lookup), forwarded to the flow. RETURNS: { id, name, status, createdDate, audience_type, async: true } — `audience_type` is the MA_CONTACTS_* you created and `id` is a creation/flow id, not associable yet.
    ConnectorAPI key
  • Run a live comment automation on comments that are **already on the post**: the ones it missed because they came before it was enabled, during an outage, or while another tool handled the account. An automation normally reacts only to new comments. How Meta works: a comment can get one private reply, and only within 7 days. Older comments cannot be reached, and a comment another app already answered by DM is refused by Meta (counted as alreadyReplied, not as a failure). Instagram and Facebook only; top-level comments only. mode preview sends nothing: it reads the newest comments and answers eligible (how many would get the automation now) and skipped by reason (mine, tooOld, keyword, alreadyRan, answered, sameAuthor). One person gets it once: when someone commented several times, only their newest comment is answered (sameAuthor counts the rest). **Always preview first, show the person the numbers, and start only after they confirm**, because a sent message cannot be recalled. mode start queues the job: comments are answered a few at a time (Meta allows 750 private replies per hour per account, shared with the live automation), so a large post takes hours. Read progress in get_automation (pastComments), and see each answered comment in list_automation_runs. mode stop halts a running job; disabling the automation stops it too. By default a comment that already has a reply from the account is skipped (answered) and the trigger's public reply is not posted; includeAnswered and publicReply change that. The automation must be live (automation_not_live); one job per automation at a time (past_comments_running); a next-post automation that has not bound to a post yet has nothing to read (past_comments_no_post).
    Connector
    Destructive
    No auth
  • Add or edit a WhatsApp HTTP, remote MCP, platform or connected-app tool after confirming the exact change. Pass id to edit and complete configuration; omit url to preserve an existing endpoint. Input schema must describe an object. Enter authentication headers in dashboard settings. Creating a tool does not enable it; assign IDs using update_whatsapp_agent updates.externalToolIds. Reuse the same idempotencyKey on retries. Requires whatsapp_agents:write.
    ConnectorOAuth
  • 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
  • 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

Matching MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    An MCP server that turns deployed n8n workflows into callable tools for AI agents, enabling discovery and execution of tagged workflows via a standard interface without rewriting integrations.
    4
    6 npm
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to review workflow status in n8n instances, including active/inactive counts and workflows with recent errors.
    1
    MIT

Matching MCP Connectors

  • n8n MCP — query your own n8n instance (BYO).

  • Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real

  • 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
  • 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.
    Connector
    Destructive
    OAuth
  • 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
  • Diagnose a failed or surprising n8n execution. Paste the execution JSON (from the n8n UI 'Show details' or `GET /executions/:id?includeData=true`); returns a per-node summary highlighting nodes that returned 0 items, unresolved `={{ ... }}` expressions, errors with hints, and LLM token usage. Hits the most common debugging pain point: items 'silently disappearing' between nodes. Deterministic, rule-based.
    ConnectorNo auth
  • Validate a GTIN / UPC / EAN barcode (GTIN-8/12/13/14) by its check digit. Catches mistyped product barcodes in inventory/catalog workflows. Pure-algorithm.
    ConnectorNo auth
  • Start a TestWell order for the user: tests/panels, the US state where they will visit the lab (required for pricing and lab routing), and the buyer's name, email and phone. Returns priced line items in cents, the single $6 lab fee, the total, any blocking messages, and pay_online_url — a prefilled cart the user can pay in a browser when the platform has no payment token. Use dry_run to preview without creating a session.
    ConnectorNo auth
  • Validate and repair an n8n workflow JSON before production. static: deterministic plus model checks of nodes, connections, credentials, expressions, reachability. simulated: synthetic dry run with safe fixtures. repair: minimal RFC 6902 JSON Patch plus a replay fixture, re-validated in-worker. Returns PASS/FAIL/REVIEW with exact node and field, stable reason codes, and an evidence packet. n8n only. Put a JSON string in query: {"mode":"static|simulated|repair", ...}. Price by mode: static $0.10 (default if mode is missing or the JSON is unparseable), simulated $0.50, repair $2.00. The payment challenge reflects the mode you send. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • 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
  • List the AI models selectable for visibility runs, per platform, with prices. Returns every platform's options (id, label, default flag, tier, credits per probe) plus a roles table mapping default / latest / prior to a concrete model id for every platform. Use the ids or role keywords in the models map or in probes[].model when creating a run. Read-only and free.
    ConnectorOAuth
  • Define a new custom post type (e.g. "treatment", "service"). Required before creating posts of that type. After creating a post type, use create_post_type_field to define its structured field schema. Those fields are stored in meta on each post — do not use excerpt for structured data.
    ConnectorNo auth
  • Define a new custom post type (e.g. "treatment", "service"). Required before creating posts of that type. After creating a post type, use create_post_type_field to define its structured field schema. Those fields are stored in meta on each post — do not use excerpt for structured data.
    ConnectorNo auth
  • Use when the buyer names an automation, form, AI voice, ad, or CRM stack and needs implementation guidance. Matches it against 53 published LeadProof platform guides and returns canonical paths and concise steps. For reliability scoring or ROI, use audit_lead_workflow or evaluate_leadproof_fit instead.
    ConnectorNo auth
  • Report feedback about the META COUNCIL PLATFORM itself — a noticeable performance failure, a lacking/missing capability, a bug, or a UX/docs gap in Meta Council's tools, councils, workflows, or MCP surface. Platform feedback only: do NOT use this for anything about your own business, customers, deals, invoices, or other data Meta Council manages on your behalf — use the relevant business tool for that instead (e.g. create_deal, create_invoice). Use it the moment a tool result, council run, or workflow falls short. Stored per-user and visible only to platform admins — the response returns an id + acknowledgement and submissions cannot be read back. Include machine context (tool name, session id, model) in the context object.
    ConnectorNo auth