Check lead visit history when Linear issues change
Use an issue update as a cue to revisit the known lead's website activity.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Get All Visits
Tool to retrieve all visits for a specific lead. use when you need detailed visit history for a lead, optionally filtered by date range.
Why this helps
A team may update a lead-related issue without checking whether the lead's website activity offers useful context for its next step.
- Bring visit history into a timely issue review.
- Reduce the chance of overlooking recent website activity.
- Keep the review focused on a lead identifier already known to the automation.
Setup
Build it in a few focused steps.
- 1Connect Linear and Leadfeeder once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to find the associated Leadfeeder lead identifier in an updated issue and retrieve that lead's visits; report when the identifier is missing.
- 4Pick the Linear Issue Updated trigger and choose where run reports should go.
- 5Test with one real issue linked to a known Leadfeeder lead.
Questions about this workflow
Does this discover a lead from an issue title alone?
No. The automation needs a Leadfeeder lead identifier available in the issue context or supplied by the user.
Can the visit history use a date range?
Get All Visits supports an optional date range. State the desired range in the prompt if the team has one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Leadfeeder. A trigger fires from one place; an action lands in another.
Linear triggers
Leadfeeder actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Accounts
Tool to retrieve a list of accounts the user has access to. use when you need to discover all available leadfeeder accounts after authentication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get All Visits
Tool to retrieve all visits for a specific lead. use when you need detailed visit history for a lead, optionally filtered by date range.
Comment Received Trigger
Triggered when a comment is received.
Get Company Info by IP
Tool to retrieve company information based on an ip address. use when you need to enrich an ip and obtain its company profile. returns 404 if no match is found.
Issue Created Trigger
Triggered when a new issue is created.
Get Custom Feeds
Tool to retrieve a list of custom feeds for a specific account. use after confirming the account id to list all its custom feed configurations.
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 Leadfeeder, 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 Leadfeeder.