Turn Stripe disputes into deadline-driven evidence tasks

Put the evidence deadline in the team's work queue

Stripe records a dispute and, when available, its evidence deadline. This example creates a high-priority Linear issue for a team you choose. The issue links to the Stripe case, shows the actual deadline in UTC, and can be due a configurable number of days earlier for internal review. A Slack message gives the team the deadline and issue link.

The Linear issue gives someone a place to gather booking records, correspondence, or other relevant evidence. A teammate still needs to read the dispute reason in Stripe, decide whether to contest it, and submit the response. If Stripe does not supply a deadline, the issue and Slack message say to check Stripe rather than inventing a date.

A short-term accommodation operator said an approximately £812 dispute was lost after the evidence deadline passed, despite having booking and checkout records.Source: A merchant's missed dispute deadline on Reddit

What you'll tell the agent

• The Stripe account where disputes arrive.
• The Linear team that handles dispute evidence.
• The Slack channel for urgent dispute handoffs.
• The number of days before Stripe's evidence deadline when the team should review the case; the example defaults to two.
• Account authorization.

The agent will create the project and ask you for these details. When Automate.ax asks you to connect an account, authorize the integrations you want this workflow to use.

The agent will set up the project and ask you to connect Stripe, Linear, and Slack. You do not need to create a Linear issue or webhook yourself.

The automation

A new Stripe dispute starts the automation. It creates a Linear issue with the Stripe case link and actual evidence deadline, sets an earlier internal due date when possible, and posts the issue to Slack.

import { automation, t } from "automate.ax"
import { linear } from "automate.ax/linear"
import { slack } from "automate.ax/slack"
import { stripe } from "automate.ax/stripe"

export default automation(
  "Track Stripe disputes before evidence is due",
  {
    parameters: [
      { label: "Linear team ID", name: "linearTeamId", type: "text" },
      {
        label: "Slack conversation ID",
        name: "slackConversationId",
        type: "text",
      },
      {
        label: "Days before evidence deadline for review",
        name: "reviewLeadDays",
        type: "number",
        defaultValue: 2,
        min: 0,
        max: 30,
        step: 1,
      },

What a run looks like

Set it up

1. Copy the setup prompt at the top into your coding agent.
2. Choose the Linear team, Slack channel, and how many days before Stripe's deadline the issue should be due. The example uses two days unless you change it.
3. Authorize Stripe, Linear, and Slack when prompted. Decide who in the Linear team will own incoming issues; this example assigns a team, not an individual.
4. Deploy and trigger a Stripe test dispute. Inspect the due date and the links in Linear and Slack before relying on the workflow for live cases.

Check the result

Trigger a Stripe test dispute and compare Stripe's UTC evidence deadline with the date in Linear and Slack. Confirm the Linear issue is due by your chosen review lead time, links to the correct case, and appears in the selected team.

Where this workflow stops

• The automation does not submit evidence to Stripe, decide whether to contest a dispute, or improve the odds of winning it.
• If the deadline is missing, the issue has no due date. If the deadline is already close, the internal due date may be today rather than your full lead time.
• The issue does not include the charge amount, dispute reason, or an individual assignee. Open the Stripe case to review those details and assign the work inside Linear.
• A missed card-network deadline cannot be repaired by creating a task afterward. Keep Stripe's own dispute notifications enabled.

Common questions