Documentation

Tools

What a workflow's steps can use — CoRoid's own tools, your business apps, your own APIs, lists — and how to get one that doesn't exist yet.

An agent's step does its work with tools: reply to the customer, look a booking up, add a lead to a list. A step only uses the tools it names, and every tool says what it does to the world:

  • reads: looks something up and changes nothing;
  • changes: changes something, such as moving a booking or sending mail;
  • money: moves money, such as a refund. Money always waits for a person's yes.

Workflows → Tools lists every tool your organization has. Owners and admins connect new ones there; every member can read the list.

CoRoid's own

  • Reply on the case channelchanges
  • Ask the customerchanges
  • Help pagesreads

Business apps

  • Gmail: Send email (Zapier)changes
  • Stripe: Create a refundmoney
  • HubSpot: Find a contactreads

Your MCP servers

  • find_orderreads
  • cancel_orderchanges

Your own APIs

  • Find a bookingreads
  • Move a bookingchanges

Lists

  • Look up in Partnersreads
  • Add to Leadschanges

Money waits

A tool that moves money always waits for a person's yes, whatever the step says.

Each tool says what it does to the world: it reads, it changes something, or it moves money.

CoRoid's own tools

Always there: reply on the case's channel, send an email, ask the customer and wait, hand the case to a person, wait until a date, create a CoRoid task, and Help pages, which looks answers up on your public help site (give its address the first time a step uses it).

Business apps

Apps your business already uses, through their makers' own MCP servers. Open one, follow its steps, and connect; its tools then appear under Your MCP servers, ready to pick in a step.

AppWhat your steps getYou need
ZapierThousands of apps through your Zapier account: Gmail, Outlook, Google Calendar, Microsoft 365, Shopify, Slack and more. Only the actions you add in Zapier become tools.A connection token from mcp.zapier.com
MakeYour Make scenarios and the apps connected to your Make organization.An API key and your zone, such as eu2.make.com
StripeCustomers, invoices, subscriptions, refunds and payment links. Every change through Stripe counts as money.An agent API key from the Stripe Dashboard
HubSpotYour CRM: contacts, companies, deals and tickets.An MCP connector in HubSpot, with CoRoid's redirect URL

A key is stored sealed and never shown again. Give a key only the access your workflows need: a Stripe key that reads customers and payments, for example, and writes only what a step should change.

Your MCP servers

Any MCP server your organization connects in Settings → Connections → MCP servers offers its tools here. A tool its server marks as read-only reads; any other tool changes things, and a payments server's tools move money.

Open a tool to say which of its inputs CoRoid fills from the case rather than the agent: a "find my orders" tool can take the customer's verified address from the case, so a message asking for someone else's orders only ever sees the sender's own.

Your own APIs

When a system has an HTTP API but no MCP server, connect it as an API tool: one call, with its method, its address, its inputs and where its key goes. Import from OpenAPI drafts tools from an OpenAPI description; nothing is saved until you connect a draft. Test makes a real call, so you see the answer before a workflow uses it. Every saved change is a new version, and a workflow keeps the version it was tried with.

Calls go through CoRoid's credential broker: the agent never sees the key.

Lists

A list is a table your workflows keep, under Workflows → Lists. A step uses it through two tools:

  • Look up in a list: finds the rows that hold the words the agent looks for, in any column or in one.
  • Add to a list: adds a row from the case. Only a list that cases add to offers it.

There are two kinds:

  • Kept by you: your prices, opening hours or partners. Steps only look rows up. Add rows by hand or import a CSV file saved from a spreadsheet.
  • Cases add rows: leads, requests, sign-ups. Each row belongs to the case that added it, and goes with it when the case is deleted.

Kept by you

Partners

  • Northwind Partners · Sweden
  • Contoso Delivery · Canada
  • Fabrikam Nord · Norway

Look up in Partnersreads

Cases add rows

Leads

  • Ada Berg · ada@example.comfrom a case
  • Bo Lind · bo@example.comfrom a case

Add to Leadschanges

A list you keep is only looked up; a list cases add to gets a row from each case, which goes with its case.

A list with a column of dates can also start cases: see At a set time.

Have CoRoid build it

When no app, server or API you have does what a step needs, choose Have CoRoid build it on the Tools page. Say what the tool should do, the system it works with and its documentation, and which of your projects builds it. CoRoid opens it as new work: an endpoint in that project that does exactly that, with a key and an OpenAPI description. You review its pull request as any work; once it is deployed, connect it with Import from OpenAPI.