See Fireberry context when Linear issues change
Issue changes can affect customer conversations. Ask Notis to look up the relevant Fireberry records and include the results in its run report.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Fireberry: Query Records
Tool to query records with filtering, sorting, and pagination. use when you need to retrieve specific fireberry records by module.
Why this helps
A status or property change in Linear can mean a customer commitment needs attention, but the CRM context may be in another app.
- Bring related CRM records into the issue follow-through process.
- Surface CRM context when issue properties change.
- Receive results in the run-report channel you choose.
Setup
Build it in a few focused steps.
- 1Connect Linear and Fireberry once in Notis.
- 2Create an automation in Automations and describe the CRM context to look up when an issue changes.
- 3Tell Notis how to identify related Fireberry records using information available in the issue, and what to include in its report.
- 4Pick the Linear Issue Updated trigger and choose where run reports go.
- 5Test with one real issue that contains the identifying information your query needs.
Questions about this workflow
What can Notis search for in Fireberry?
The query needs criteria that match your Fireberry records. Describe which available issue details to use, such as a customer name or identifier, and confirm those details are present in your setup.
Does this update Fireberry records?
This workflow queries records and reports the results. Its selected Fireberry action does not edit records.
What if an issue does not identify a customer?
Notis needs a reliable identifier to find related records. Supply one in the issue or describe another available way to identify the records.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Fireberry. A trigger fires from one place; an action lands in another.
Linear triggers
Fireberry actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a new Fireberry record
Tool to create a new record in a specified fireberry table. use when you have the table name and record data ready for insertion.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Picklist Values
Tool to retrieve all possible picklist (dropdown) values for a specific field. use when you need to load all available options for a picklist field in a record type.
Comment Received Trigger
Triggered when a comment is received.
Fireberry: Query Records
Tool to query records with filtering, sorting, and pagination. use when you need to retrieve specific fireberry records by module.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Fireberry, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Fireberry.