[ More ]
NocoDB integration for your workflows.
Connect NocoDB to Collabase once and use 5 actions in your workflows. No code needed, hosted in Switzerland.
NocoDB in Collabase
Connect NocoDB to Collabase once and use 5 actions in your workflows. No code needed, hosted in Switzerland.
How to connect it
- Open the integrations in the workspace settings.
- Choose NocoDB and connect your account.
- Add a trigger or an action to the workflow.
- Log in to your NocoDB Account.
- Click on your profile-pic(bottom-left) and navigate to Account Settings->Tokens.
- Create new token with any name and copy API Token.
- Your Base URL is where your app is hosted.
NocoDB triggers
NocoDB does not start a workflow on its own. You use its actions after any other trigger.
NocoDB actions
| Name | Description | Fields |
|---|---|---|
| Create a Record | Creates a new record in the given table. |
|
| Delete a Record | Deletes a record with the given Record ID. |
|
| Update a Record | Updates an existing record with the given Record ID. |
|
| Get a Record | Gets a record by the Record ID. |
|
| Search Records | Returns a list of records matching the where condition. |
+ 1
|
[ More ]
Related integrations
Tools that often share a workflow.
Questions about NocoDB
What can I automate with NocoDB in Collabase?
NocoDB brings 5 actions and 0 triggers, for example Create a Record, Delete a Record, Update a Record, Get a Record and 1 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect NocoDB to Collabase?
You open the integrations in the workspace settings, choose NocoDB and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.
Does the NocoDB 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.