Keep Linear campaign follow-up current with Braze
Turn a recurring Braze status check into a small, useful update on the Linear issue tracking the campaign.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Update issue
Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.
Why this helps
Teams can lose track of campaign follow-up when status checks and next steps are scattered across tools.
- Refresh an existing issue with relevant campaign context
- Keep follow-up visible in the team's work queue
- Reduce repeated manual status checks
Setup
Build it in a few focused steps.
- 1Connect Braze and Linear once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe the outcome in one instruction: review the specified Braze campaign status and update the identified Linear issue with a concise status and next step.
- 4Choose a recurring schedule as the trigger.
- 5Choose where run reports go, then test with one real campaign and issue.
Questions about this workflow
Does this create a new Linear issue each time?
No. This workflow updates an existing issue. Identify that issue clearly in the instruction or provide its identifier in the run context.
What should the automation change?
Tell Notis what status information and next step belong in the issue. The update action requires a change to at least one issue attribute.
What if Braze does not expose the status detail I need?
The workflow can only use information available to the run. Supply missing context in the instruction or run input, or narrow the update to available campaign details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Braze to Linear. A trigger fires from one place; an action lands in another.
Braze triggers
Linear actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a comment
Creates a new comment on a specified linear issue.
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Braze and Linear, 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 Linear.