Keep Failed Payment Follow-Up Moving
When a Stripe payment intent fails, give your team one clear place to track the next recovery step.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Create a task
Creates a new clickup task in a specific list, optionally as a subtask if a `parent` task id (which cannot be a subtask itself and must be in the same list) is provided.
Why this helps
Failed payments can sit unnoticed while someone figures out who should contact the customer and what to do next.
- Capture failed payment follow-up in ClickUp
- Give the team a visible next step
- Reduce manual checks across Stripe and ClickUp
Setup
Build it in a few focused steps.
- 1Connect Stripe and ClickUp once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to create a ClickUp task for each failed payment intent, summarizing the available payment details and suggesting a follow-up.
- 4Pick the Stripe Payment Intent Failed trigger and choose where run reports should go.
- 5Test with one real failed payment example.
Questions about this workflow
What starts this automation?
A Stripe payment intent failure event starts it.
What happens in ClickUp?
Notis creates a task with a summary based on the information Stripe provides.
Can Notis choose who should handle recovery?
Notis can use instructions you provide, but the event may not contain enough information to determine an owner.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Clickup. A trigger fires from one place; an action lands in another.
Stripe triggers
Clickup actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add dependency
Adds a 'waiting on' or 'blocking' dependency to a task, requiring either `depends on` (task becomes waiting on) or `dependency of` (task becomes blocking), but not both; `team id` is required if `custom task ids` is true.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add guest to folder
Adds a guest to a folder with specified permissions; requires a clickup enterprise plan.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Add guest to list
Shares a clickup list with an existing guest user, granting them specified permissions; requires the workspace to be on the clickup enterprise plan.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Add guest to task
Assigns a guest to a task with specified permissions; requires clickup enterprise plan, and `team id` if `custom task ids` is true.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Add tags from time entries
Associates a list of specified tags with one or more time entries within a given team (workspace).
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Add tag to task
Adds an existing tag to a specified task; team id is required if custom task ids is true.
Product Created Trigger
Triggered when a product is created in Stripe
Add task link
Links two existing and accessible clickup tasks, identified by `task id` (source) and `links to` (target).
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Add task to list
Adds an existing task to an additional clickup list; the "tasks in multiple lists" clickapp must be enabled in the workspace for this.
Connect any two apps with Notis in the middle.
Stripe and Clickup, 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 Clickup.