Aidbase currently provides 8 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Email Received
Fires when a new email is received in an Aidbase inbox.
Email Status Changed
Fires when the status of an email changes.
Email Priority Changed
Fires when an email’s priority is changed.
Email Sent
Fires when an email is sent from Aidbase.
Ticket Created
Fires when a new ticket is created in Aidbase.
Ticket Priority Changed
Fires when the priority of an existing ticket changes.
Ticket Status Changed
Fires when a ticket’s overall status changes.
Ticket New Comment
Fires when a new comment is added to an existing ticket.
Add Video
Adds a YouTube video URL as knowledge to the Aidbase knowledge base.
Add Website
Adds a website URL as a knowledge source for Aidbase.
Add FAQ Item
Adds a new question/answer item to an existing FAQ; supports categories.
Create FAQ
Creates a new FAQ entry with title and description.
Create Chatbot Reply
Generates an AI chatbot reply given a message and optional session context.
Start Training
Starts a training job on an existing knowledge base item (FAQ, website, video, etc.).
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Aidbase event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Email Received
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Aidbase action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Add Video
Combine Aidbase with another integration and Coherence records to connect support activity to the full account history and the next internal action.
Starts with
Email Received
Finishes with
Add Video, then preserve the outcome in Coherence
The exact authentication fields depend on Aidbase. The workflow structure stays straightforward:
Authorize the Aidbase account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Aidbase or provide a complementary trigger or action.
Aidbase currently provides 8 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Aidbase currently lists 8 triggers and 7 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Aidbase triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
