Automatic Customer Context for Feature Requests
Feature requests arrive without customer company context so prioritization decisions lack context. This automation pulls customer profiles instantly.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Company Find
Tool to lookup company data by domain name. use when you need detailed company profile by providing a website domain. use after confirming domain correctness.
Why this helps
Feature requests lack customer company context, forcing prioritization decisions without understanding who is requesting and why it matters.
- Requesting customer company auto-researched when request is created
- Prioritization is informed by who is asking
- Product decisions have customer context built in
Setup
Build it in a few focused steps.
- 1Open Notis and create a feature request automation
- 2Name it (e.g. 'Feature request customer context') and describe: 'When a feature request issue is created, find the customer company in Bigpicture io'
- 3Select trigger: Issue Created (filter to 'feature-request' label or 'feature' in title)
- 4Describe how to identify the customer (name, email, domain, etc.)
- 5Test with a real feature request
Questions about this workflow
What if a feature request comes from multiple customers?
Notis can research each one. Your prompt describes what to do: create a list, track separately, or aggregate similar requests.
Can I prioritize based on company size or industry?
Yes. Bigpicture io provides company details that Notis can use to inform prioritization. Describe your criteria in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Bigpicture io. A trigger fires from one place; an action lands in another.
Linear triggers
Bigpicture io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Company Find
Tool to lookup company data by domain name. use when you need detailed company profile by providing a website domain. use after confirming domain correctness.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
IP to Company Lookup
Tool to lookup company by ip address. use after obtaining an ip to get detailed company info.
Comment Received Trigger
Triggered when a comment is received.
Name to Domain Search
Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.
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 Bigpicture io, 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 Bigpicture io.