Connect Linear to Brex
When something happens in Linear, Notis takes the next step in Brex. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Linear to Brex
Automate Expense Creation from Issues
Create Brex expenses automatically when Linear issues are marked expense-ready
Check Available Budgets When Projects Start
Review all available budgets in Brex when a new Linear project is created
Issue Cards to New Team Members Automatically
Create Brex cards automatically when onboarding issues are created in Linear
Get Daily Spend Report Delivered Automatically
Receive a summary of all Brex transactions from the past 24 hours every morning
Pull Budget Details When Concerns Are Raised
Automatically retrieve budget details from Brex when budget concerns are flagged in Linear
Create Departments in Brex from Linear Issues
Automatically create Brex departments when new department issues are created in Linear
Pull Vendor List When Discussion Occurs
Retrieve all vendors from Brex when vendor discussions happen in Linear comments
Review All Cards When Security Concerns Arise
Automatically list all company cards from Brex when security issues are flagged in Linear
Isolate Travel Spending in Transaction Reports
Get travel card transactions when travel expenses are logged as Linear issues
Supported Triggers and Actions
Notis builds workflows that link Linear to Brex. A trigger fires from one place; an action lands in another.
Linear triggers
Brex actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Budget
Create a new budget for departments or projects.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Card
Create a new card and assign it to a user.
Comment Received Trigger
Triggered when a comment is received.
Create Department
Create a new department.
Issue Created Trigger
Triggered when a new issue is created.
Create Expense
Create a new expense.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create Location
Create a new location.
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).
Create Job Title
Create a new job title.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Create User
Create a new user in the brex account.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Create Vendor Card
Create a new vendor card.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Linear and Brex
Connect any two apps with Notis in the middle.
Linear and Brex, 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 Brex.