Fireberry
Create or update Fireberry CRM records with field mappings and connections.
The Fireberry action (CRM integration) reads and writes Fireberry tables: pick a table, an action, identify the record (except on create), then define actions (field updates) and connections (linked records).
When to use
- Sync workflow data into CRM objects (leads, deals, custom tables).
- Create records when none exist, or update existing rows.
- Link records through Fireberry connection fields with Query by field.
Configuration
| Field | What it does | When to use |
|---|---|---|
| Table | Fireberry object type (objectType); loads fields on select | Choose the CRM entity |
| Action | Create, Update Record, or Create If None Exist | Match upsert vs always-create semantics |
| Object ID | CRM field that identifies the record + variable binding | Required for update / create-if-none; hidden for Create |
| Action N (green) | Set a field on the table to a value, selection, or variable | Map workflow data into columns |
| Connection N (blue) | Link to another object via a connection field | Relate records (account → contact, etc.) |
| Description | Canvas note | Team documentation on the canvas |
Action types
| Value | Behavior |
|---|---|
| Create | New record; no Object ID section |
| Update Record | Update existing record identified by Object ID + variable |
| Create If None Exist | Create only when lookup via Object ID finds nothing |
Object ID
- Choose a field from the table (searchable list: label ·
fieldName). - Bind Object ID value with the variable tree from upstream nodes.
Action rows (field updates)
Each Add Action row:
- Field — searchable Fireberry column on the selected table.
- Value — depends on field type:
- Most fields: variable/expression tree picker.
- Selection box fields: choose value source — Selection box (pick enum value), Variable (fixed binding), or Expression.
Use Add Action for normal field writes. Rows are labeled Action 1, Action 2, …
Connection rows
Each Add Connection row links via a connection field:
- Pick the connection field on the main table.
- If valid, configure Query by field on the linked object type (loads related table fields).
- Set the connection value like action rows (including selection-box sources).
- Invalid connection fields show Not a connection field (red border).
Connections use a distinct background in the form and count separately (Connection 1, …).
Changing Table clears existing queries and reloads fields (refresh available on section headers).
Flow behavior
- Input: After triggers/actions that supply variables for Object ID and field values.
- Output: Single default edge.
- Field metadata and picklists load asynchronously (loading indicators on table/field sections).
Examples
Update deal stage from message keyword
- Table → Deals.
- Action → Update Record.
- Object ID → deal id from trigger variable.
- Add Action → stage field ← variable from If / Else branch.
Create contact linked to account
- Action → Create.
- Add Action → map name, phone from customer variables.
- Add Connection → account lookup field + Query by field + account id variable.