Feature Requests Trigger Research Call Campaigns
Feature requests pile up. Instead of reading them solo, your agent calls the requesters to understand their pain point deeply, validate the idea, and learn about alternatives they've tried.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Schedule batch by id
Schedule a batch for calling via agent
Why this helps
Feature requests come in but you never talk to customers about them. You build based on assumptions. You ship features customers don't actually want. Build and learn cycles are slow.
- You learn customer pain directly instead of guessing from requests
- Features are validated before building, saving weeks of wasted effort
- Customers feel heard; their feature requests lead to real conversations
Setup
Build it in a few focused steps.
- 11. Connect Linear and Bolna to Notis.
- 22. Create an automation: 'When 3+ feature requests arrive in a week, schedule research calls with the requesters.'
- 33. Tell Notis the research questions: 'Ask about their pain point, alternatives tried, and how often they need this.' Notis guides the calls.
- 44. Set the trigger to 'Issue Created' (feature-request type) and choose Slack.
- 55. Test by creating 3 feature request issues and verify research call batches are scheduled.
Questions about this workflow
Should the agent call requesters individually or do group interviews?
Your choice. Say: 'Call each person individually to keep conversations personal' or 'Do group calls to find common patterns.' Notis arranges it.
What if requesters don't want to be called?
Tell Notis: 'Send a message asking if they'd like a quick call, then only call those who agree.' Notis respects consent.
Can Notis summarize the calls and flag common feature requests?
Yes. Tell Notis: 'After each call, post a summary in an issue comment. Flag if 5+ people asked for the same thing.' Notis aggregates patterns.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Bolna. A trigger fires from one place; an action lands in another.
Linear triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
Comment Received Trigger
Triggered when a comment is received.
Fetch all batches by agent id
List all batches for agent
Issue Created Trigger
Triggered when a new issue is created.
Get all agents
List all agents
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get all phone numbers
List all phone numbers for your account
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).
Get execution by id
Retrieve specific execution by `execution id`
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Make a phone call from agent
Initiate calls
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Retrieve agent by id
Retrieve an agent
Connect any two apps with Notis in the middle.
Linear and Bolna, 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 Bolna.