Call action template reference

What it is

The complete list of Call Action templates, grouped the way the template gallery groups them, with what each one does and the credential it asks for.

Every template here is a Custom API action with the request already built. For how templates work in general — where to find them, how the setup panel guides you, and what "write-only secret" means — read Use a preset first. This page is the lookup table you come back to.

Two columns to read carefully:

• Credential is what you go and fetch from the other service before you start.
• Confirmation tells you whether the template ships with Requires confirmation on. On means the visitor must confirm on their next message before anything is actually created. Templates that only read data ship with it off.

Where to find it

Open Dashboard → Chatbots → your chatbot → Actions → New action, then scroll to Or start from a template. Use Search integrations… to jump straight to a brand.

Each tile opens the editor with a What you'll need panel: the exact steps for that service and a Read the docs link to the provider's own documentation. That panel is authoritative for setup detail; this page is the overview.

Scheduling

Template	What it does	Credential	Confirmation
Cal.com	Books a meeting on your Cal.com calendar from a time, name, email, and time zone the visitor gave.	Bearer token — a Cal.com API key from Settings → Security.	On
Calendly	Creates a single-use Calendly scheduling link and gives it to the visitor.	Bearer token — a Calendly personal access token from Integrations → API & Webhooks.	On

Cal.com's older API was retired in April 2026, so this template targets the current one and ships with the version header it requires — leave that header in place. Calendly links are single-use by design: the chatbot creates a fresh one each time, so you also need the API address of the event type you want booked.

CRM and leads

Template	What it does	Credential	Confirmation
HubSpot	Adds a contact to your HubSpot CRM from an email, plus first and last name when known.	Bearer token — a HubSpot Private App access token with contact write access.	Off

HubSpot's old-style API keys no longer work; create a Private App and copy its access token.

Support desks

Template	What it does	Credential	Confirmation
Zendesk	Creates a support ticket with a subject, the customer's description, and their name and email.	Basic auth — your Zendesk email with /token appended as the username, and an API token as the password.	On
Freshdesk	Creates a Freshdesk ticket, opening at status Open and priority Low.	Basic auth — your API key as the username and any character (such as X) as the password.	On
Intercom	Adds a contact to Intercom from an email and optional name.	Bearer token — an Intercom access token from the Developer Hub.	On

Zendesk's /token suffix on the username is the single most common cause of a 401 here — without it the request is rejected. Both Zendesk and Freshdesk need your own subdomain substituted into the address. The Intercom template ships with the API version header the service requires.

Chat and notifications

Template	What it does	Credential	Confirmation
Slack	Posts a message the chatbot writes into a Slack channel.	None — the incoming-webhook URL is itself the secret.	Off
Discord	Posts a message into a Discord channel.	None — the channel webhook URL is the secret.	Off
Microsoft Teams	Posts a formatted card into a Teams channel.	None — a Power Automate workflow URL is the secret.	Off

All three are webhook-based: you create the webhook in the other product, paste the URL as the request address, and choose no authentication. Anyone holding that URL can post to your channel, so never share it or paste it into a public page.

For Teams, the old Office 365 connector has been retired — create the webhook through Workflows on the channel instead. The template already carries the card format Teams now expects.

Do not confuse these with the Slack and Discord channels, which are a different feature: a channel is somewhere your customers talk to your chatbot, while these templates push a one-way message from it into your own workspace. See Connect Slack and Connect Discord.

If you would rather alert your team by email than by chat, use the Notify team action type instead; it needs no webhook at all.

E-commerce

Template	What it does	Credential	Confirmation
Shopify — draft order	Creates a draft order from a product name, price, quantity, and customer email.	API key header — a Shopify Admin API access token from a custom app with draft-order write access.	On
Shopify — order status	Reads one order's payment and fulfilment status and total.	API key header — an Admin API access token with order read access.	Off
WooCommerce — find a product	Searches your catalogue by name or SKU so the chatbot can quote a live price.	Basic auth — a WooCommerce REST consumer key and consumer secret with Read permission.	Off
WooCommerce — check an order	Reads one order's status and total from its order number.	Basic auth — consumer key and secret, Read permission.	Off
WooCommerce — create an order	Creates an order from a product ID, quantity, and email. It opens unpaid for you to process.	Basic auth — consumer key and secret with Read/Write permission.	On
Salla — find a product	Searches your Salla catalogue by keyword.	Bearer token — a Salla merchant access token with product read access.	Off
Salla — check an order	Reads one Salla order's status from its order ID.	Bearer token — merchant access token with order read access.	Off
BigCommerce — find a product	Searches your BigCommerce catalogue by name or SKU.	API key header — a store-level API account access token with product read-only scope.	Off
Magento — find a product	Searches your Adobe Commerce / Magento catalogue by product name.	Bearer token — an integration access token with catalogue read access.	Off
PrestaShop — find a product	Searches your PrestaShop catalogue by product name.	Basic auth — the webservice key as the username, blank password.	Off

Notes that save time:

• All the store templates need your own domain, subdomain, or store hash substituted into the address, and your store must be reachable over HTTPS.
• Grant the narrowest scope that works. The look-up templates only need read access; only the two order-creating templates need write.
• Salla merchant access tokens expire after 14 days. Plan to refresh the credential, or the action will start failing.
• Magento needs a setting enabled in your admin before an integration token works as a bearer token; the setup panel names it.
• PrestaShop returns XML unless the JSON format is requested — that is already in the template's address, so leave it there.
• These templates are separate from Agentency's storefront plugins, which do a different job. See Shopify and storefronts and Salla and Zid.

Shipping and tracking

Template	What it does	Credential	Confirmation
AfterShip	Looks up a shipment's live status and checkpoints across 1,000+ carriers, from a carrier slug and tracking number.	API key header — an AfterShip API key.	Off
EasyPost	Looks up a shipment's live status from a tracking number.	Basic auth — your EasyPost API key as the username, blank password.	Off
DHL	Looks up a DHL shipment's status and events from a tracking number.	API key header — a DHL developer-portal subscription key.	Off

AfterShip needs the carrier as well as the number, so make sure your action's description tells the chatbot to ask which courier. EasyPost gives the best results when the relevant carrier accounts are added on their side.

Marketing and email

Template	What it does	Credential	Confirmation
Mailchimp	Adds a subscriber to a Mailchimp audience with optional first and last name.	Basic auth — any username, with your API key as the password.	Off
SendGrid	Sends an email with a subject and body the chatbot composes.	Bearer token — a SendGrid API key with Mail Send permission.	On

Mailchimp needs both your data-centre suffix and your audience ID substituted into the address; both are visible in your Mailchimp account. SendGrid needs a verified sender address written into the template body — an unverified sender is rejected outright.

Only add a subscriber when the visitor actually asked to subscribe. Describe that precondition in the action's trigger description.

Productivity and project management

Template	What it does	Credential	Confirmation
Notion	Creates a page in a Notion database with a title from the conversation.	Bearer token — an internal Notion integration token.	On
Airtable	Creates a record in an Airtable base with a name and notes.	Bearer token — an Airtable personal access token with record-write scope.	On
Jira	Creates a Jira issue as a Task on a project you name.	Basic auth — your Atlassian account email as the username and an API token as the password.	On
Asana	Creates an Asana task with a name, optional notes, and a project.	Bearer token — an Asana personal access token.	On

Notion has an extra step people miss: creating the integration is not enough, you must also share the target database with it. Your database's title property must be named Name, or edit the request body to match yours. Airtable needs the base added to the token's access list, plus your base ID and table name in the address, and the field names in the body must match your table exactly. Asana needs your project's ID passing through as a parameter.

Web search

Template	What it does	Credential	Confirmation
Brave Search	Searches the web so the chatbot can answer with current information that is not in its knowledge.	API key header — a Brave Search subscription token (a free tier exists).	Off

This is the one template that changes what the chatbot knows rather than what it does. It is genuinely useful for time-sensitive facts, and genuinely risky if you rely on it for anything about your own business — web results are not your knowledge base and are not cited the same way. Keep your own facts in Knowledge and use search only for the outside world.

Automation bridges

Template	What it does	Credential	Confirmation
Zapier	Posts a message, name, and email to a Zapier Catch Hook, which can then fan out to thousands of apps.	None — the webhook URL is the secret.	Off
Make	Posts the same shape to a Make custom webhook scenario.	None — the webhook URL is the secret.	Off

These two are the escape hatch for anything not on this page. Services that require an OAuth sign-in flow, form-encoded bodies, or GraphQL cannot be templated directly, so route them through a Zap or a Make scenario instead. Add or rename fields in the request body to match what your automation expects, and run the scenario once so Make learns the data shape. See Zapier and Make.

What you will see

The gallery renders each template as a tile with the brand's logo, its name, and a one-line description, grouped under the headings above. Selecting one opens the standard action editor — Details, Configure, Test — pre-filled, with the What you'll need panel at the top of Configure.

Limits and plan notes

• Each template you enable counts as one of your enabled Call Actions: Free 0, Starter 3, Standard 8, Pro 12, Agency 20 per chatbot. See Plans and what you get.
• Every template calls a public service over the internet. Private and internal addresses are refused, and a run against one is recorded as Blocked destination.
• Each call has a few seconds to answer before it is recorded as Timed out, and repeated failures against the same endpoint pause it briefly rather than hammering it.
• Secrets are write-only. Once saved they are never displayed again; leave a secret field blank when editing to keep what is stored.
• Agentency does not maintain your credentials. Expired tokens, revoked scopes, and rotated keys surface as failed runs in the Call Action history.

Common problems

A brand I need is missing.

Use the Zapier or Make bridge, or build it yourself with HTTP connectors.

Everything returns 401 or 403.

The credential style or its scope is wrong. Re-read the What you'll need panel — Basic auth in particular differs per service, and several of these want the key in the username field rather than the password.

It worked, then stopped.

A token expired or was rotated, or the provider changed something. Open the Run log, read the error, and re-paste the credential. Salla tokens in particular expire on a two-week cycle.

The right template exists but fires at the wrong time.

The pre-filled trigger description is a starting point, not a finished one. Rewrite it in the words your visitors use, and name what must already be known before the action may run.