Keep failed Stripe payments from slipping through the cracks
When a payment intent fails, give the follow-up a clear place in Bitbucket.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
Why this helps
Failed payments can get buried in Stripe activity, leaving follow-up scattered across tabs and memory.
- Create a trackable issue as soon as a payment intent fails.
- Keep payment follow-up alongside the work your team already manages in Bitbucket.
- Reduce manual checking of Stripe events.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction how to turn a failed payment intent into a Bitbucket issue with relevant event context.
- 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 Failed event starts it.
Does Notis let me configure field mappings?
No. Describe the outcome in plain language, and Notis uses the event context to create the issue.
Can I review whether the automation ran?
Yes. Choose a report channel during setup to receive run reports.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Bitbucket. A trigger fires from one place; an action lands in another.
Stripe triggers
Bitbucket actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a branch
Creates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Create a pull request
Creates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Create repository
Creates a new bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project key` is not provided.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
Product Created Trigger
Triggered when a product is created in Stripe
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Delete repository
Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.
Connect any two apps with Notis in the middle.
Stripe and Bitbucket, 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 Bitbucket.