Fireberry currently provides 1 trigger that can start a workflow and 4 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Record Created or Updated
Fires when a record is created or updated in Fireberry.
Create Record
Create a new record in Fireberry.
Update Record
Update an existing record in Fireberry.
Delete Records
Delete records from Fireberry.
Find Records
Search for records in Fireberry.
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 Fireberry event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Record Created or Updated
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Fireberry 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
Create Record
Combine Fireberry with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
Record Created or Updated
Finishes with
Create Record, then preserve the outcome in Coherence
The exact authentication fields depend on Fireberry. The workflow structure stays straightforward:
Authorize the Fireberry 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 Fireberry or provide a complementary trigger or action.
Fireberry currently provides 1 trigger that can start a workflow and 4 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Fireberry currently lists 1 trigger and 4 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 Fireberry 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.
