External Payment Events Auto-Sync to Linear
Send payment events from your custom backend or third-party tools to Notis via webhook, and it automatically updates related Linear issues with status changes, refunds, and confirmations.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a comment
Creates a new comment on a specified linear issue.
Why this helps
Your custom backend processes Stripe webhooks but your ops team never knows about them. Results and decisions are trapped in logs or Slack. Linear stays out of sync with actual payment status.
- Any payment event from your backend can update Linear instantly via webhook
- Sync external systems (accounting software, custom APIs) without manual intervention
- Flexible—configure it however your backend sends data
- Real-time visibility into payment lifecycle across all systems
Setup
Build it in a few focused steps.
- 1Connect Stripe and Linear to Notis.
- 2Create an automation: 'Webhook Payment Status Sync'.
- 3Prompt: 'When a webhook arrives with a payment event (refund, dispute, confirmation), find the related Linear issue by customer email or invoice ID and add a comment with the event details and timestamp.'
- 4Set the trigger to 'notis_webhook'—Notis will provide you a unique webhook URL.
- 5Post that webhook URL to your backend and test by sending a sample payment event.
Questions about this workflow
How do I send a webhook from my backend?
Notis will give you a URL endpoint. POST JSON to that URL with payment event data (customer, amount, event type). Notis will parse it and update Linear.
Can I send events from multiple systems to the same webhook?
Yes—Notis can handle different event formats if you describe them in your prompt. It'll extract the right data from each.
What if the webhook payload doesn't match a Linear issue?
Tell Notis what to do: create a new issue, log it to Slack, or skip it. You control the fallback behavior.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Linear. A trigger fires from one place; an action lands in another.
Stripe triggers
Linear actions
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Create a comment
Creates a new comment on a specified linear issue.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Product Created Trigger
Triggered when a product is created in Stripe
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Not just Stripe and Linear. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Linear.