Each integration in Cargofy gives the assistant one tool per action, named integration-<integration>-<action>. Your assistant sees the same list in every account. An action works when your brand has that integration connected.
- Changes data: yes for actions that send or write, no for actions that only read
- Who can use it: any member of the brand. Some sending actions also need a send permission in your role.
What it is for
- Send an email through the Cargofy integration, with an exported list attached. See Email.
- See which integrations are connected first with
config-integrations-list.
Example prompts
- “Email the warehouse at demo@example.com that the truck arrives on Tuesday at 14:00.”
Good to know
- An action of an integration that is not connected answers “No connected '…' integration for this brand.”
- A connection that needs signing in again answers “The connection needs to be re-authorized.”
- A send from Cargofy answers
ok: truewhen the email is accepted. - “Connection not found for this brand and integration.” for a wrong
connection_id. Missing required input '…' for operation '…'.when a required field is left out or empty.- Each action describes its own fields in your assistant. The assistant reads them from the tool’s description.
Reference
Parameters
Every action takes:
| Name | Type | Required | Description |
|---|---|---|---|
connection_id | string | no | Which connection to use. Needed when your brand has more than one connection of this integration. |
Plus the action’s own fields.
Returns
data of the call.
Email from Cargofy
| Tool | What it does | Changes data |
|---|---|---|
integration-cargofy-send_email | Sends an email from Cargofy to one or more recipients. Fields: to (comma-separated), subject, body; optional attachment_file_ids — for example the file_id of a list exported with entities-query | yes |
json
{ "data": { "ok": true, "recipients": ["demo@example.com"], "attachments": 0 } }