Step 2: Connect Stripe and Pull Dispute Data

Fetch disputes from Stripe using the HTTP request node configured for Stripe API credentials.

1. Open Retrieve Stripe Disputes and set URL to https://api.stripe.com/v1/disputes.
2. Set Authentication to predefinedCredentialType and Credential Type to stripeApi.
3. Credential Required: Connect your stripeApi credentials.
4. Connect Retrieve Stripe Disputes to Verify Dispute Records.

Step 3: Filter and Transform Dispute Records

Filter out empty responses and transform the Stripe payload into a normalized format for notifications and tasks.

1. In Verify Dispute Records, add a condition with Left Value set to {{ $json.data && $json.data.length > 0 }} and Right Value set to true.
2. Connect the true output of Verify Dispute Records to Transform Dispute Payload.
3. Connect the false output of Verify Dispute Records to Dispatch Status Summary to send a “no new disputes” update.
4. In Transform Dispute Payload, keep the provided JavaScript Code as-is to compute formatted_amount, priority, days_until_deadline, and other normalized fields.

Step 4: Route by Urgency and Send Slack Notifications

Use conditional logic to route urgent disputes to a high-priority Slack alert and all others to a standard notification.

1. In Assess Urgency Level, set the condition Left Value to {{ $json.data[0].status }} and Right Value to needs_response.
2. Connect the true output of Assess Urgency Level to Post Urgent Slack Notice.
3. Connect the false output of Assess Urgency Level to Send Standard Slack Notice.
4. In Post Urgent Slack Notice, keep the Text field as the provided expression starting with =🚨 **HIGH PRIORITY DISPUTE ALERT** 🚨.
5. Credential Required: Connect your slackApi credentials to Post Urgent Slack Notice, Send Standard Slack Notice, and Dispatch Status Summary.

Assess Urgency Level routes to either Post Urgent Slack Notice or Send Standard Slack Notice based on dispute status.

Step 5: Create ClickUp Tasks for Dispute Handling

Create ClickUp tasks with the correct priority and due date based on the transformed dispute data.

1. Connect Post Urgent Slack Notice to Create High Priority Task.
2. In Create High Priority Task, set List, Team, and Space to your IDs (replace [YOUR_ID] values).
3. Set Name to =🚨 URGENT: Dispute {{ $json.dispute_id }} - {{ $json.formatted_amount }} and Due Date to {{ $json.evidence_deadline }}.
4. Connect Send Standard Slack Notice to Create Regular Task.
5. In Create Regular Task, set Name to =Dispute: {{ $json.dispute_id }} - {{ $json.formatted_amount }} and Priority to {{ $json.priority === 'High' ? '1' : ($json.priority === 'Medium' ? '2' : '3') }}.
6. Credential Required: Connect your clickUpApi credentials to Create High Priority Task and Create Regular Task.

Post Urgent Slack Notice leads to Create High Priority Task, while Send Standard Slack Notice leads to Create Regular Task.

Step 6: Test and Activate Your Workflow

Run a manual test to validate Stripe data retrieval, routing, Slack notifications, and ClickUp task creation.

1. Click Execute Workflow and run from Manual Execution Start.
2. Confirm that Retrieve Stripe Disputes returns dispute data and Verify Dispute Records routes correctly.
3. Check Slack for either Post Urgent Slack Notice or Send Standard Slack Notice, or the Dispatch Status Summary if no disputes exist.
4. Verify ClickUp tasks created in Create High Priority Task or Create Regular Task with correct titles and due dates.
5. When the workflow is working as expected, toggle the workflow to Active for production use.