Check customer context as issues are created
When a new issue includes customer context, let Notis look for a possible Landbot record and bring the result into your report channel.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
List Customers
Tool to list customers who have interacted with your bot. use when you need to retrieve customer records with optional filters (channel id, opt in, search) and pagination.
Why this helps
Customer context may be buried in a new issue while the corresponding Landbot record takes another search and tab switch to find.
- Checks for matching customer records at intake
- Reduces repetitive lookups
- Keeps potential matches easy to confirm
Setup
Build it in a few focused steps.
- 1Connect Linear and Landbot to Notis once through the portal.
- 2Create an automation through the portal or tell Notis the desired result conversationally.
- 3Give Notis one instruction to search the Landbot customer list using clear customer clues from a new issue, then report possible matches.
- 4Select the Linear Issue Created trigger and choose a run-report channel.
- 5Test with a real issue that includes a customer clue.
Questions about this workflow
What if the issue has no customer clue?
The prompt can ask Notis to report that there is not enough information to search rather than guess.
Are returned records confirmed matches?
They are possible matches and should be checked before using them for follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Landbot. A trigger fires from one place; an action lands in another.
Linear triggers
Landbot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Bot
Tool to delete a specific bot from your account. use when you need to remove an unused or test bot after confirming the bot id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Customer By Phone
Tool to retrieve customer details by phone number. use when you need to fetch a customer's profile by their phone. example: "find customer with phone +1234567890".
Comment Received Trigger
Triggered when a comment is received.
List Agents
Tool to retrieve a list of agents in your landbot account. use after authenticating your account to enumerate all agents and their details.
Issue Created Trigger
Triggered when a new issue is created.
List Bots
Tool to list all bots in your landbot account. use after authenticating to discover your configured bots.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List Channels
Tool to list all channels integrated with your account. use after authenticating your account to enumerate available messaging channels and metadata.
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).
List Customers
Tool to list customers who have interacted with your bot. use when you need to retrieve customer records with optional filters (channel id, opt in, search) and pagination.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
List WhatsApp Templates
Tool to list all whatsapp message templates available for the account. use after obtaining your whatsapp channel id to fetch template ids and parameter counts.
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 Landbot, 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 Landbot.