[ More ]
Cody integration for your workflows.
Connect Cody to Collabase once and use 7 actions in your workflows. No code needed, hosted in Switzerland.
Cody in Collabase
Connect Cody to Collabase once and use 7 actions in your workflows. No code needed, hosted in Switzerland.
How to connect it
- Open the integrations in the workspace settings.
- Choose Cody and connect your account.
- Add a trigger or an action to the workflow.
Cody triggers
Cody does not start a workflow on its own. You use its actions after any other trigger.
Cody actions
| Name | Description | Fields |
|---|---|---|
| Create Document From Text | Upload text content to create a new document within the Cody knowledge base. |
|
| Upload File to Knowledge Base | Add a file directly into a specific folder in the knowledge base. |
|
| Send Message | Send your message and receive the AI-generated response. |
|
| Create Conversation | Creates a new conversation with a bot. |
|
| Find Bot | Finds a bot based on its name. |
|
| Find Conversation | Finds a conversation based on its name and/or the bot it belongs to. |
|
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ More ]
Related integrations
Tools that often share a workflow.
Questions about Cody
What can I automate with Cody in Collabase?
Cody brings 7 actions and 0 triggers, for example Create Document From Text, Upload File to Knowledge Base, Send Message, Create Conversation and 3 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect Cody to Collabase?
You open the integrations in the workspace settings, choose Cody and connect your account once, using an API key. After that all triggers and actions are available in the workflow.
Does the Cody integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.