Keep Linear issues current with Clay enrichment
When Clay supplies new context, place the update in the Linear issue where the follow-up is being tracked.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a comment
Creates a new comment on a specified linear issue.
Why this helps
New enrichment can be missed when teams must remember to revisit Clay and manually refresh an existing issue.
- Keep existing issue context fresh as research changes.
- Avoid creating duplicate issues for the same follow-up.
- Make new information visible in the issue's conversation.
Setup
Build it in a few focused steps.
- 1Connect Clay and Linear once in the Notis portal.
- 2Create an automation in Automations, New Automation, and instruct Notis to add incoming enrichment as a concise issue comment.
- 3Choose the Notis webhook trigger and configure Clay to send the update with the identifier for the existing issue.
- 4Choose where run reports go, then test with one real enrichment update.
Questions about this workflow
Does this replace the issue description?
No. It adds a comment so the update is visible without overwriting the existing issue description.
What if the issue identifier is missing?
Notis needs enough information in the webhook request to find the intended existing Linear issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clay to Linear. A trigger fires from one place; an action lands in another.
Clay 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.
Clay 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.