Keep agent context visible as projects shift
When project ownership or timing changes, bring the Landbot agent roster into the run report for easier coordination.
Trigger
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
Action
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.
Why this helps
Project handoffs can add mental overhead when agent context is spread across separate tools.
- Adds roster context to project change reviews
- Helps founders spot coordination questions sooner
- Avoids an extra manual Landbot lookup
Setup
Build it in a few focused steps.
- 1Connect Linear and Landbot to Notis once through the portal.
- 2Create the automation via the portal or ask Notis to configure it from a natural-language request.
- 3Use one instruction asking Notis to list Landbot agents and summarize the roster when a project property changes.
- 4Select the Linear Project Properties Updated trigger and choose a run-report channel.
- 5Test after a real project lead or status change.
Questions about this workflow
Will this reassign project owners or Landbot agents?
No. It only retrieves the Landbot agent roster and provides it as context.
Which changes are relevant?
It can run on project property updates; the prompt should explain which project context is useful to include in the report.
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.