n8n Workflow: Automated Stripe Dispute Alert & Case Tracking with Slack & ClickUp

This n8n workflow streamlines the process of handling Stripe disputes by automatically alerting your team and creating a new task in ClickUp for case tracking. It ensures that no dispute goes unnoticed and that a structured process is initiated immediately.

What it does

This workflow automates the following steps:

1. Manual Trigger: The workflow is initiated manually, typically for testing or ad-hoc dispute processing.
2. HTTP Request: It makes an HTTP request, likely to a Stripe API endpoint, to retrieve dispute information.
3. Code (Data Transformation): Processes the data received from the HTTP request, extracting relevant details about the dispute.
4. Conditional Logic (If): Evaluates the dispute data. Although the specific condition is not visible in the JSON, it likely checks for a particular status or type of dispute that requires immediate action.
5. Slack Notification (True Branch): If the condition is met (e.g., a new, high-priority dispute), a notification is posted to a designated Slack channel, alerting the team.
6. ClickUp Task Creation (True Branch): Simultaneously, a new task is created in ClickUp to track the dispute resolution process, assign responsibilities, and manage deadlines.

Prerequisites/Requirements

To use this workflow, you will need:

• n8n Instance: A running instance of n8n.
• Stripe Account: Access to your Stripe account API for fetching dispute data.
• Slack Account: A Slack workspace and a channel for dispute notifications.
• ClickUp Account: A ClickUp workspace, space, and list where dispute tasks will be created.
• API Keys/Credentials:
  • Stripe API Key (for the HTTP Request node)
  • Slack API Token/Webhook URL (for the Slack node)
  • ClickUp API Token (for the ClickUp node)

Setup/Usage

1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
2. Configure Credentials:
   • For the HTTP Request node, configure the URL to your Stripe API endpoint for disputes and set up the necessary authentication (e.g., Bearer Token with your Stripe Secret Key).
   • For the Slack node, select or create a Slack credential. You'll need to specify the channel where alerts should be posted and customize the message content using expressions from the previous nodes.
   • For the ClickUp node, select or create a ClickUp credential. Specify the Workspace ID, Space ID, and List ID where tasks should be created. Map the dispute details to the task name, description, and other fields as needed.
3. Customize the Code Node: Review and adjust the JavaScript code in the "Code" node to correctly parse and format the dispute data from Stripe according to your needs. This is crucial for extracting the right information for Slack and ClickUp.
4. Configure the If Node: Define the conditions in the "If" node that determine whether a dispute should trigger Slack and ClickUp actions. For example, you might check {{ $('HTTP Request').item.json.status }} for specific dispute statuses.
5. Activate the Workflow: Once configured, activate the workflow.
6. Test the Workflow: Manually execute the workflow using the "When clicking ‘Execute workflow’" trigger to ensure all steps are working as expected and that notifications and tasks are created correctly. For real-world usage, you would typically replace the manual trigger with a webhook or scheduled trigger that listens for new Stripe dispute events.