Live

SuiteDash logo

SuiteDash API and MCP server

suitedash.com

SuiteDash has a Secure API for Super Admins and Admins, with monthly call caps, but its Zapier app only covers contacts, companies, projects and tasks (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for SuiteDash with 14 endpoints (6 read, 8 write): your AI agent signs in as you and does the work.

Endpoints
14 6 read, 8 write
Updated
How Cotlet connects your agent to SuiteDash
  1. Your agent

    Claude Code, Codex, Cursor or a script

  2. Cotlet

    MCP server and REST API · 14 endpoints

    cotlet.dev/mcp/v1

  3. SuiteDash logo

    SuiteDash

    Signed in as you on suitedash.com

You sign in once. We never store your password.

Official API

Does SuiteDash have an official API?

SuiteDash has a Secure API for Super Admins and Admins, with monthly call caps, but its Zapier app only covers contacts, companies, projects and tasks (checked 11 Oct 2026). No official endpoint or Zapier action creates invoices, records payments, sends portal messages or shares files.

What SuiteDash's own tools do compared with Cotlet
Task SuiteDash official Cotlet
Find and create contacts Yes Zapier: Find Contacts, Create Contact, Update Contact Yes
Create projects Yes Zapier: Create Project, Update Project Yes
Add and complete tasks Partly Zapier: Create Task, Update Task; no invoice or message link Yes
List and read invoices No Yes
Create and send invoices No Yes
Record invoice payments No Yes
Read and send portal messages No Yes
Share files with a client No Yes

Sources: SuiteDash Help: Secure API · SuiteDash Help: Office Invoices · SuiteDash Help: A.I. Agents and Skills · SuiteDash Help: Project Generators · SuiteDash file sharing for clients · SuiteDash triggers and actions on Zapier

Common use cases

What can an AI agent do in SuiteDash?

Cotlet is best for agencies and freelancers on SuiteDash who want their AI agent to handle invoices, payments, portal messages and client onboarding without running or fixing a server.

  • Create and send client invoices Runs: Weekly

    Invoice Acme Studio for the 10 design hours from last week at $90, due in 14 days. Check I have not billed them for it already, then send it. Your agent calls find_contact, list_invoices and create_invoice.

  • Chase overdue invoices Runs: Weekly

    Which invoices are still open and past due, and who owes the most? Your agent calls list_invoices and get_invoice.

  • Record bank transfer and check payments Runs: Weekly

    Here are this week's bank deposits. Match them to my open SuiteDash invoices, record the payments as Bank Transfer, and list who is still past due. Your agent calls list_invoices, get_invoice and record_payment.

  • Onboard a new client

    New client Jane from client@example.com: add her, open a Website Redesign project and add the kickoff tasks. Your agent calls create_contact, create_project and add_task.

  • Reply to client portal messages Runs: Daily

    Go through my unread SuiteDash messages, answer the deadline questions from the task due dates, and show me drafts before anything is sent. Your agent calls list_message_threads, list_tasks and send_message.

Endpoints

What is the SuiteDash API?

Cotlet's SuiteDash API exposes 14 endpoints for your own SuiteDash account: find contact, list projects, list tasks, list invoices, get invoice, list message threads, create contact, create project, add task, complete task, create invoice, record payment, send message and share file. The find_contact endpoint returns contacts and companies by name or email, with role, company and custom fields. Each endpoint takes simple JSON inputs like client_id, role or project_id and works both as an MCP tool for agents and as a REST call for scripts.

All endpoints · 14 total

missing one? request an endpoint

  • POST

    find_contact

    read

    Searches your CRM by name, company name or email and returns the matches with their UID, role and company. Use the UID as client_id or contact_id in the other tools. Role is Lead, Prospect or Client as in your CRM.

    POST /api/v1/suitedash/find_contact

    Input

    Input: find_contact
    Parameter Type Description
    query required string Name, company name or email.
    role enum lead, prospect or client. Default: any.

    Example response

    {
      "contacts": [
        {
          "contact_id": "c7f2a9e1-4b3d-4e8a-9f10-2d6b5a8c3e71",
          "name": "Ana Lopez",
          "email": "ana@acmestudio.example",
          "role": "client",
          "company": "Acme Studio"
        }
      ]
    }
  • POST

    list_projects

    read

    Lists projects, optionally for one client. Archived projects are left out unless you ask. Use project_id in add_task and list_tasks.

    POST /api/v1/suitedash/list_projects

    Input

    Input: list_projects
    Parameter Type Description
    client_id string Only projects of this contact or company.
    include_archived boolean Include archived projects. Default: false.

    Example response

    {
      "projects": [
        {
          "project_id": "p_2201",
          "name": "Website Redesign",
          "client": "Acme Studio",
          "status": "In progress",
          "leader": "you@yourcompany.example",
          "start_date": "2026-10-12",
          "completion_date": "2026-12-01"
        }
      ]
    }
  • POST

    list_tasks

    read

    Lists tasks across your account, or in one project. Set mine_only to see your My Tasks list. Completed tasks are left out unless you ask.

    POST /api/v1/suitedash/list_tasks

    Input

    Input: list_tasks
    Parameter Type Description
    project_id string Only tasks in this project.
    mine_only boolean Only tasks assigned to you (My Tasks). Default: false.
    include_completed boolean Include completed tasks. Default: false.

    Example response

    {
      "tasks": [
        {
          "task_id": "t_8841",
          "title": "Kickoff call",
          "project": "Website Redesign",
          "assigned_to": "you@yourcompany.example",
          "due_date": "2026-10-14",
          "priority": "Normal",
          "status": "Open"
        }
      ]
    }
  • POST

    list_invoices

    read

    Lists invoices from Office, newest first. Filter by status, client or due date to find what is overdue. Total and amount paid are in the invoice currency, so a partial payment shows what is still owed.

    POST /api/v1/suitedash/list_invoices

    Input

    Input: list_invoices
    Parameter Type Description
    status enum draft, open, partially_paid or paid. Default: open.
    client_id string Only invoices of this client.
    due_before date Only invoices due before this date.

    Example response

    {
      "invoices": [
        {
          "invoice_id": "58213",
          "invoice_number": "1042",
          "client": "Acme Studio",
          "title": "Website design, October",
          "total": "900.00",
          "paid": "0.00",
          "currency": "USD",
          "due_date": "2026-10-10",
          "status": "open"
        }
      ]
    }
  • POST

    get_invoice

    read

    Returns one invoice with its line items, payments recorded so far and the payment link your client uses. Read it before record_payment to check what is still owed.

    POST /api/v1/suitedash/get_invoice

    Input

    Input: get_invoice
    Parameter Type Description
    invoice_id required string Invoice ID from list_invoices.

    Example response

    {
      "invoice_id": "58213",
      "invoice_number": "1042",
      "status": "open",
      "title": "Website design, October",
      "items": [
        {
          "item": "Design hour",
          "quantity": 10,
          "rate": "90.00",
          "amount": "900.00"
        }
      ],
      "total": "900.00",
      "paid": "0.00",
      "payments": [],
      "currency": "USD",
      "due_date": "2026-10-24",
      "payment_link": "https://yourname.suitedash.com/pay/invoice/58213"
    }
  • POST

    list_message_threads

    read

    Lists Secure Messaging threads in a folder, most recent first, with the last message and an unread flag. The folder is Inbox unless you name another. Use thread_id to reply with send_message.

    POST /api/v1/suitedash/list_message_threads

    Input

    Input: list_message_threads
    Parameter Type Description
    folder string Folder name. Default: Inbox.
    unread_only boolean Only threads with unread messages.
    limit integer 1 to 50. Default: 20.

    Example response

    {
      "threads": [
        {
          "thread_id": "th_3a91",
          "subject": "Deadline for the logo files",
          "participants": [
            "Ana Lopez"
          ],
          "last_message": "Can we move the deadline to Friday?",
          "unread": true,
          "updated_at": "2026-10-09T15:40:00Z"
        }
      ]
    }
  • POST

    create_contact

    write

    Adds one contact to your CRM and links it to a company, creating the company if it does not exist. No portal invitation or email goes out, and one edit in SuiteDash undoes it, so this tool runs without asking.

    POST /api/v1/suitedash/create_contact

    Input

    Input: create_contact
    Parameter Type Description
    first_name required string First name.
    last_name required string Last name.
    email required string Email address.
    role required enum lead, prospect or client.
    company_name string Company to link, created if it does not exist.

    Example response

    {
      "contact_id": "c7f2a9e1-4b3d-4e8a-9f10-2d6b5a8c3e71",
      "name": "Jane Doe",
      "role": "client",
      "company": "Doe Studio",
      "status": "created"
    }
  • POST

    create_project

    write

    Creates a project for one client. With task_template, the project gets that template's tasks and phases. Nothing is sent to the client, and the project can be archived afterwards, so this tool runs without asking.

    POST /api/v1/suitedash/create_project

    Input

    Input: create_project
    Parameter Type Description
    name required string Project Name.
    client_id required string Client UID from find_contact.
    task_template string Task Template name; adds its tasks and phases.
    start_date date Project Start Date.
    completion_date date Estimated Completion Date.
    estimated_value string Estimated value, e.g. "2500 USD".

    Example response

    {
      "project_id": "p_2201",
      "name": "Website Redesign",
      "client_id": "c7f2a9e1-4b3d-4e8a-9f10-2d6b5a8c3e71",
      "status": "created",
      "start_date": "2026-10-12",
      "completion_date": "2026-12-01"
    }
  • POST

    add_task

    write

    Adds a task to a project, or a standalone task when project_id is empty. It is assigned to you unless you give a staff email. Priority uses the names in your account. Runs without asking: the task reaches only your team and complete_task closes it.

    POST /api/v1/suitedash/add_task

    Input

    Input: add_task
    Parameter Type Description
    title required string Task title.
    project_id string Project from list_projects. Empty: standalone task.
    assigned_to string Staff email. Default: you.
    due_date date Due Date.
    priority string Priority as named in your account. Default: Normal.
    description string Task description.

    Example response

    {
      "task_id": "t_8841",
      "title": "Kickoff call",
      "project_id": "p_2201",
      "assigned_to": "you@yourcompany.example",
      "due_date": "2026-10-14",
      "status": "created"
    }
  • POST

    complete_task

    write

    Marks one task as Completed. It runs without asking, because it reaches no client and one edit in SuiteDash reopens the task.

    POST /api/v1/suitedash/complete_task

    Input

    Input: complete_task
    Parameter Type Description
    task_id required string Task ID from list_tasks.

    Example response

    {
      "task_id": "t_8841",
      "status": "completed"
    }
  • POST

    create_invoice

    write

    Creates an invoice for one client from items set up in Office, with a due date. The total is the sum of quantity times rate. With status draft nothing is sent. With status open the client can pay it, and notify_client sends the New Invoice notification. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/suitedash/create_invoice

    Input

    Input: create_invoice
    Parameter Type Description
    client_id required string Client UID from find_contact.
    title required string Title visible to the client.
    items required object List of { item, quantity, rate }. item is an Item from Office settings.
    due_date required date Due Date.
    status enum draft or open. Default: draft.
    notify_client boolean Send the New Invoice notification when open. Default: true.

    Example response

    {
      "invoice_id": "58213",
      "invoice_number": "1042",
      "status": "open",
      "total": "900.00",
      "currency": "USD",
      "due_date": "2026-10-24",
      "payment_link": "https://yourname.suitedash.com/pay/invoice/58213"
    }
  • POST

    record_payment

    write

    Records a manual payment on one invoice, with a Payment Type from your account and an optional note. A partial amount leaves the invoice partially paid. send_confirmation emails the standard payment confirmation to the client. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/suitedash/record_payment

    Input

    Input: record_payment
    Parameter Type Description
    invoice_id required string Invoice ID from list_invoices.
    amount required string Amount paid, e.g. "900.00".
    payment_type required string Payment Type as named in your account, e.g. Bank Transfer.
    note string Payment note.
    send_confirmation boolean Email the payment confirmation. Default: false.

    Example response

    {
      "invoice_id": "58213",
      "payment_id": "pay_7710",
      "amount": "900.00",
      "payment_type": "Bank Transfer",
      "invoice_status": "paid",
      "confirmation_sent": true
    }
  • POST

    send_message

    write

    Sends a Secure Messaging message: a reply when thread_id is set, otherwise a new thread to the contacts or staff in to, with a subject. Messages go out under your name. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/suitedash/send_message

    Input

    Input: send_message
    Parameter Type Description
    to string[] Contact UIDs or staff emails. Required for a new thread.
    thread_id string Reply in this thread from list_message_threads.
    subject string Subject of a new thread.
    body required string Message text.

    Example response

    {
      "thread_id": "th_3a91",
      "message_id": "msg_5502",
      "status": "sent",
      "sent_at": "2026-10-11T09:05:00+02:00"
    }
  • POST

    share_file

    write

    Uploads one file from a URL to the dedicated Sharing Folder of one client. With notify, the client is told about the new file. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/suitedash/share_file

    Input

    Input: share_file
    Parameter Type Description
    contact_id required string Contact UID from find_contact.
    file_url required string Public or signed URL of the file to upload.
    notify boolean Notify the contact about the new file. Default: true.

    Example response

    {
      "contact_id": "c7f2a9e1-4b3d-4e8a-9f10-2d6b5a8c3e71",
      "file_name": "acme-logo-final.zip",
      "status": "shared",
      "notified": true
    }

Setup

How do I connect SuiteDash to Claude Code, Codex or Cursor?

Connecting SuiteDash takes three steps: request access, sign in to SuiteDash once, then add one MCP server or call the REST API with the same key.

Connect SuiteDash over MCP

  1. 1

    Create an account

    Sign up and add SuiteDash in the console. Your API key is there too.

  2. 2

    Sign in to SuiteDash once

    Open the connect page from the console and sign in to SuiteDash the way you always do. We keep the session, never your password, and you can revoke it anytime.

  3. 3

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

  4. 4

    Ask your agent

    Prompt

    Invoice Acme Studio for the 10 design hours from last week at $90, due in 14 days. Check I have not billed them for it already, then send it.

    Ask in plain words. Your agent finds the SuiteDash tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

Call SuiteDash over REST

  1. 1

    Export your API key

    Shell

    export COTLET_API_KEY="cotlet_..."

    Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

  2. 2

    Call a tool

    curl

    curl https://cotlet.dev/api/v1/suitedash/create_invoice \
      -H "Authorization: Bearer $COTLET_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"client_id":"c7f2a9e1-4b3d-4e8a-9f10-2d6b5a8c3e71","title":"Website design, October","items":[{"item":"Design hour","quantity":10,"rate":90}],"due_date":"2026-10-24","status":"open","notify_client":true}'

    Every tool is a POST endpoint at /api/v1/suitedash/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

  3. 3

    Read the result

    Example response · create_invoice

    {
      "invoice_id": "58213",
      "invoice_number": "1042",
      "status": "open",
      "total": "900.00",
      "currency": "USD",
      "due_date": "2026-10-24",
      "payment_link": "https://yourname.suitedash.com/pay/invoice/58213"
    }

    You get plain JSON back, ready for your script. A failed call costs nothing.

Why Cotlet

Why use Cotlet for SuiteDash? Hosted, safe and kept working.

  • Built for agents

    • One MCP server for every app you connect.
    • The same tools as a REST API for scripts and cron jobs.
    • Works with Claude Code, Codex and Cursor.
  • Your login stays yours

    • You sign in to SuiteDash yourself. We keep only the session, encrypted with AES-256.
    • The model never sees a login.
    • No stored passwords, no CAPTCHA solving, no MFA bypass.
  • You stay in control

    • Pick read only, or read and write.
    • Anything that reaches other people waits for your OK, unless you switch it off per tool.
    • Revoke access in one click.
  • Kept working for you

    • We test every integration daily.
    • When SuiteDash changes, the tool pauses until we fix it.
    • Failed calls cost nothing.

Alternatives

Is there a SuiteDash MCP server on GitHub?

The SuiteDash Zapier app creates and updates contacts, companies, projects and tasks with your Secure API keys, and hosted connectors from other platforms cover contacts and companies. None of them touch invoices, payments, messages or files, so for those jobs the realistic option is doing it by hand in the portal.

Cotlet compared with a Zapier
Zapier Cotlet
Setup Paste your Secure API Public ID and Secret Key into Zapier, then build each Zap Request access, sign in to SuiteDash once, add one MCP server or API key
Invoices and payments No action for them List, create and send invoices and record payments, each send confirmed by you
Messages and files No action for them Read threads, send portal messages and share files, confirmed by you
Agent use Fixed Zaps you build ahead of time Your agent picks the tools: Claude Code, Codex, Cursor, n8n and scripts
API call cap Secure API calls count toward your plan cap (400 a month on Start) Works in your account like you do; no Secure API keys needed
When SuiteDash changes Maintained by SuiteDash and Zapier Our team tests it daily and fixes it for you; failed calls are free
Price Free Zapier tier, paid plans for multi-step Zaps Free 7-day trial with 5,000 credits, then credits per call

Which one fits you

Pick Cotlet if

  • you are not a developer, or you do not want to maintain a server
  • you need it to keep working when SuiteDash changes, without checking it yourself
  • your agent or a script should run it on a schedule, also while your computer is off

Pick an open-source server if

  • you are comfortable installing, updating and fixing it yourself
  • you want the session to stay on your own computer
  • you only need it now and then, from one MCP client

For AI agents

Cotlet for SuiteDash in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Endpoint health

verified 2h ago

  • find_contact passing
  • list_projects passing
  • list_tasks passing
  • list_invoices passing
  • get_invoice passing

+ 9 more endpoints

14/14 passing latest check self-healing

suitedash.txt

SuiteDash has a Secure API for Super Admins and Admins, with monthly call caps, but its Zapier app only covers contacts, companies, projects and tasks (checked 11 Oct 2026). No official endpoint or Zapier action creates invoices, records payments, sends portal messages or shares files.
Cotlet provides a hosted MCP server and REST API for SuiteDash: 14 tools (6 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=suitedash; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/suitedash
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        find_contact, list_projects, list_tasks, list_invoices, get_invoice, list_message_threads, create_contact, create_project, add_task, complete_task, create_invoice, record_payment, send_message, share_file
Confirm      create_invoice, record_payment, send_message, share_file (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/suitedash-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=suitedash (SuiteDash is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to SuiteDash once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted SuiteDash server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to SuiteDash in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following SuiteDash's terms; Cotlet is not affiliated with SuiteDash.
Full page as Markdown

Automations

Can SuiteDash automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a SuiteDash connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to create and send client invoices, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

Where to run SuiteDash automations through Cotlet, and how to schedule them
Where How to connect How to schedule
Your AI agent Add https://cotlet.dev/mcp/v1 with your API key. A scheduled agent run, for example a Claude Code routine.
n8n MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/suitedash/{tool}. Schedule Trigger node.
Make HTTP module: POST https://cotlet.dev/api/v1/suitedash/{tool} with an Authorization: Bearer header and a JSON body. Scenario schedule.
Zapier Webhooks by Zapier: POST https://cotlet.dev/api/v1/suitedash/{tool} with the same header and body. Schedule by Zapier trigger.
Your own script POST https://cotlet.dev/api/v1/suitedash/{tool} with your API key. cron or GitHub Actions.

Pricing & limits

How much does the SuiteDash API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the SuiteDash API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

Cotlet plan sizes: price, monthly credits and price per credit
Size Price Credits / month Per credit
Solo $29/mo 3,000 about $0.0097
Pro $99/mo 12,000 about $0.0083
Agency $299/mo 40,000 $0.0075

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.

About Cotlet

How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own SuiteDash account.

Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to SuiteDash yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a SuiteDash tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect SuiteDash in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do
Store passwords, solve CAPTCHAs or bypass MFA.
SuiteDash's terms
You use your own SuiteDash account and stay responsible for following SuiteDash's terms. Cotlet is independent and not affiliated with SuiteDash. Terms
Contact
Questions about the company, security or an app: contact@cotlet.dev
About Cotlet

Frequently asked questions

How do I get access?

Request access and pick SuiteDash. Cotlet reviews each request and emails you your API key.

Do I need to be technical?

No. You sign in to SuiteDash once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

Is a hosted server safe? My SuiteDash session would leave my computer.

Cotlet keeps your SuiteDash session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

Do I need Secure API keys or a higher SuiteDash plan?

No. Cotlet works in your own SuiteDash account after you sign in once, so it does not use the Secure API Public ID and Secret Key or count against its monthly call cap (80 on Free Trial, 400 on Start, 2,000 on Thrive, 20,000 on Pinnacle). Invoices and payments need an admin role.

Can my agent post or send messages in SuiteDash without asking me?

No. Every call to create_invoice, record_payment, send_message or share_file waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_contact, create_project, add_task, complete_task runs without asking, because it sends nothing to anyone and one call undoes it.

Can I use the SuiteDash API in n8n?

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/suitedash/{tool} from the HTTP Request node.

Give your agent access to SuiteDash.

Request access and pick it. We review each request and email you your API key. Free 7-day trial with 5,000 credits, no card needed.