🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home n8n Workflow
January 22, 2026

ClickUp to Stripe, invoices sent and tracked via Gmail

Lisa Granqvist Partner Workflow Automation Expert

Invoices slip through when billing depends on “remembering to do it later.” One status change in ClickUp, a few tabs, a Stripe draft, an email to the client, then a separate note to your team. Something always gets missed.

Agency owners feel it when projects pile up. Ops managers get tired of chasing “did we invoice them?” threads. And freelancers are the ones eating the cost when they forget. This ClickUp Stripe invoices automation turns a ClickUp status update into a sent invoice and a team confirmation email.

Below you’ll see exactly what this workflow does, what you need, and how the flow works so you can set it up once and stop babysitting billing.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: ClickUp to Stripe, invoices sent and tracked via Gmail

Why This Matters: Invoices That Depend on Memory

Most teams don’t have an “invoicing problem.” They have a handoff problem. A task gets moved to “Ready to invoice,” then someone has to open it, find the client email, confirm the amount, create (or locate) the Stripe customer, build the invoice, add line items, send it, and finally tell the team it went out. When you’re busy, that chain breaks. The result is awkward follow-ups, delayed cash, and invoices that go out with wrong totals or missing context.

It adds up fast. Here’s where it breaks down.

  • ClickUp status changes happen in seconds, but invoicing can sit untouched for days if it’s not tied to that moment.
  • Copy-pasting client details from a task into Stripe invites small mistakes that turn into big back-and-forth.
  • Line items get entered inconsistently, which makes reporting messy and client questions harder to answer.
  • Your team doesn’t get a reliable “invoice sent” receipt, so people keep checking Stripe manually.

What You’ll Build: ClickUp Status → Stripe Invoice + Gmail Receipt

This workflow watches ClickUp for a task status change and only runs when the task hits your invoicing-ready status. Once triggered, it pulls the task details (client name, email, and the project cost you’ve stored in ClickUp). With that info, it creates or updates the customer in Stripe, then builds an invoice using Stripe’s API (via HTTP requests), including your description and footer. Next, it adds the invoice line item with the correct amount in cents (Stripe’s format), sends the invoice to the client, and wraps up by emailing your team through Gmail with the key details and a direct link back to the ClickUp task. Clear, traceable, and consistent.

The workflow starts in ClickUp, not in Stripe. It validates the status first, then assembles everything needed to create the customer and invoice. Finally, it sends two messages: the invoice to the client and a confirmation email to your team.

What You’re Building

Expected Results

Say you send 10 invoices a week. Manually, it’s easy to spend about 20 minutes per invoice between ClickUp, Stripe, double-checking amounts, and emailing the team, which is roughly 3 hours weekly. With this automation, the “work” becomes moving a task to the right status plus a quick spot-check, maybe 2–3 minutes each. The Stripe creation and sending happens in the background. That’s a couple hours back most weeks, and invoicing stops being a recurring mental tax.

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • ClickUp to trigger from task status changes
  • Stripe to create and send invoices
  • Gmail account access (connect it inside n8n credentials)

Skill level: Intermediate. You’ll connect accounts and paste API details for Stripe’s HTTP requests.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A ClickUp task changes status. The workflow uses a ClickUp trigger that listens for updates, then checks if the new status matches your “ready to invoice” stage.

The workflow pulls the task details. It retrieves the task and extracts the fields you care about (client name, email, project cost). If your ClickUp setup uses custom fields, this is where you map them.

Stripe gets the customer and invoice created. n8n creates the Stripe customer, then builds the invoice through HTTP requests, calculates the due date in a Stripe-friendly timestamp, and adds a line item with the amount converted into cents.

Two messages go out. Stripe sends the invoice to the client, and Gmail sends an internal receipt to your team with the invoice context plus a link back to the ClickUp task.

You can easily modify ClickUp statuses to match your pipeline, or swap the team notification email for a different destination. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the ClickUp Trigger

This workflow starts when a ClickUp task status changes. You’ll configure ClickUp Update Trigger to listen for the correct team and list.

  1. Add the ClickUp Update Trigger node to your workflow.
  2. Set Team to 90151078626.
  3. Set Events to taskStatusUpdated.
  4. Set Filters → List ID to 901510285394.
  5. Select Authentication as oAuth2.
  6. Credential Required: Connect your ClickUp OAuth2 credentials.
Tip: Ensure the ClickUp list and statuses match your billing process so the trigger only fires for invoice-ready tasks.

Step 2: Add Status Validation and Task Retrieval

Next, Validate Invoice Status checks the status change and Retrieve ClickUp Task pulls full task details used for Stripe and email steps.

  1. In Validate Invoice Status, set the condition Left Value to {{$json.history_items[0].after.status}}.
  2. Set the condition Operator to equals and Right Value to send invoice.
  3. Configure Retrieve ClickUp Task with Operation set to get.
  4. Set ID to {{ $('ClickUp Update Trigger').item.json.task_id }}.
  5. Select Authentication as oAuth2.
  6. Credential Required: Connect your ClickUp OAuth2 credentials.
⚠️ Common Pitfall: If the ClickUp status name doesn’t exactly match send invoice, the workflow stops at Validate Invoice Status.

Step 3: Set Up Stripe Customer and Invoice Creation

These nodes create a Stripe customer and draft invoice using data from the ClickUp task.

  1. Configure Generate Stripe Customer with Resource set to customer and Operation set to create.
  2. Set Name to {{ $json.name }} and Additional Fields → Email to {{ $json.creator.email }}.
  3. Credential Required: Connect your Stripe credentials.
  4. In Build Stripe Invoice, set URL to https://api.stripe.com/v1/invoices and Method to POST.
  5. Enable Send Query and set Authentication to predefinedCredentialType with Credential Type stripeApi.
  6. Set query parameters: collection_method = send_invoice, customer = {{ $json.id }}, description = Thanks for working with SaviFlow!, due_date = {{ $today.toSeconds() +604800 }}, footer = This is the very cool footer.
  7. Credential Required: Connect your Stripe API credentials for Build Stripe Invoice.

Step 4: Add Line Items and Dispatch the Invoice

Once the invoice is created, the workflow adds a line item and sends the invoice from Stripe.

  1. Configure Add Invoice Line with URL https://api.stripe.com/v1/invoiceitems and Method POST.
  2. Enable Send Query and set Authentication to predefinedCredentialType with Credential Type stripeApi.
  3. Set query parameters: customer = {{ $('Generate Stripe Customer').last().json.id }}, amount = {{ $('Retrieve ClickUp Task').last().json.custom_fields[1].value *100 }}, description = Thanks for building the coolest automation with SaviFlow, currency = {{ $json.currency }}, invoice = {{ $json.id }}.
  4. Credential Required: Connect your Stripe API credentials for Add Invoice Line.
  5. In Dispatch Invoice, set URL to =https://api.stripe.com/v1/invoices/{{ $('Build Stripe Invoice').item.json.id }}/send and Method to POST.
  6. Set Authentication to predefinedCredentialType with Credential Type stripeApi.
  7. Credential Required: Connect your Stripe API credentials for Dispatch Invoice.

Step 5: Configure Team Notification Email

After the invoice is sent, Notify Team via Email informs your team with task and client details.

  1. Set Send To to {{ $('Retrieve ClickUp Task').item.json.custom_fields[0].value }}.
  2. Set Subject to New invoice has been sent.
  3. Set Email Type to text.
  4. Set Message to Hello Team,

    A new invoice was dispatched to {{ $('Retrieve ClickUp Task').item.json.name }}.

    View the task: https://app.clickup.com/t/{{ $('ClickUp Update Trigger').item.json.task_id }}
    .
  5. Credential Required: Connect your Gmail OAuth2 credentials.

Step 6: Test and Activate Your Workflow

Validate the end-to-end flow from ClickUp to Stripe and email before turning it on.

  1. Manually execute the workflow using a ClickUp task that transitions to send invoice status.
  2. Confirm Retrieve ClickUp Task returns the expected custom fields for email recipient and invoice amount.
  3. Verify Stripe creates a customer, invoice, adds line item, and sends the invoice after Dispatch Invoice.
  4. Check that Notify Team via Email sends the notification email to the correct recipient.
  5. When everything looks correct, toggle the workflow to Active for production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

  • ClickUp credentials can expire or lack workspace access. If the trigger stops firing, check your ClickUp connection in n8n Credentials and confirm the right Workspace/Space permissions.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Stripe API calls via HTTP Request are picky about formats. If invoices create but totals look wrong, confirm you’re converting amounts into cents and sending the expected currency fields.

Quick Answers

What’s the setup time for this ClickUp Stripe invoices automation?

About 30–60 minutes if your ClickUp fields are already clean.

Is coding required for this invoice sending automation?

No. You’ll connect accounts and paste/configure a few Stripe API details in the HTTP Request nodes.

Is n8n free to use for this ClickUp Stripe invoices workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Stripe’s standard fees (and any email provider limits if you send a lot).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this ClickUp Stripe invoices workflow for different use cases?

Yes, and you probably should. You can change the “Validate Invoice Status” rule to match your own ClickUp pipeline, and map different custom fields in the “Retrieve ClickUp Task” step. If you want quotes instead of invoices, you’d swap the Stripe invoice HTTP requests for the relevant Stripe object. Common tweaks include different due dates, adding multiple line items, or notifying a different internal mailbox.

Why is my Stripe connection failing in this workflow?

Usually it’s an API key issue or the wrong Stripe mode. Confirm you’re using the correct secret key in the HTTP Request headers, and double-check you’re not trying to send real invoices while the account is in test/developer mode. Also watch for missing required fields like currency, customer ID, or amounts not being in cents. If it fails only sometimes, you may be hitting rate limits when several tasks flip status at once, so add basic retry handling.

What volume can this ClickUp Stripe invoices workflow process?

On n8n Cloud you’re mainly limited by your plan’s monthly executions, and by ClickUp/Stripe API limits. If you self-host, there’s no platform execution cap, so it mostly depends on server size and how many invoices you send per hour.

Is this ClickUp Stripe invoices automation better than using Zapier or Make?

Often, yes, because this flow leans on conditional logic and multiple Stripe API calls, which can get awkward (or expensive) in simpler tools. n8n is also easier to extend when you want “if client is enterprise, set different terms” style rules. Zapier or Make can still work if you keep it very basic, but you’ll hit limits sooner as your invoicing rules grow. The bigger factor is ownership: n8n can be self-hosted, so you’re not paying per tiny step forever. If you’re torn, Talk to an automation expert and we’ll map the cheapest path.

Once this is running, invoicing becomes a ClickUp habit, not a separate job. The workflow handles the repetitive parts, and you get your time back for work that actually moves revenue.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Launch login modal Launch register modal