A fee marked for billing on the board becomes a Stripe invoice, for the right customer
When a fee item on a monday.com board is set to bill, a Make scenario finds the customer in Stripe or creates them, adds the invoice item, raises the invoice and writes it back to the board. It has been running since September 2024.
Where this applies
Professional-services firms and agencies that track fees on a monday.com board and bill through Stripe.
- runs, 18 Sep to 21 Oct 2026, no errors
- 26
- paths: existing customer or new
- 2
- in use since
- Sep 2024
The problem
Firms that track their work on a board and take payment through Stripe end up re-keying: the fee is agreed on the board, then someone opens Stripe, finds or creates the customer, builds the invoice and copies its details back. Each step is small; together they are where an invoice is raised for the wrong customer, or twice, or not at all.
The trap is the customer. Create a new Stripe customer every time and the same client ends up as several records with their invoices spread across them. Search first, and the scenario needs a clean path for both answers.
What we built
The board status is the trigger
The scenario listens for changes on the fee board, reads the item and lets through only those set to bill.
Find the customer before anything else
It searches Stripe for the customer, and a router takes one of two paths. For an existing customer it goes straight to invoicing. For a new one it reads the client's details from the board and creates the Stripe customer first.
Invoice item, then invoice
On both paths the scenario creates the invoice item and then the invoice, so the two branches end in the same place and the rest of the run does not need to know which one it took.
Written back where staff look
The invoice is written back to the item's columns, so the board shows that the fee has been billed without anyone opening Stripe.
The outcome
Live since September 2024. From 18 September to 21 October 2026 it ran 26 times without an error, using 107 credits.
Because the customer is searched for before anything is created, a returning client is invoiced on their existing Stripe record.
Where it stops
It raises the invoice and records it; whether the client has paid is not brought back to the board by this scenario. A client Stripe's search does not find is created as a new customer, so the match is only as good as the details on the board.
Built with
- Make.com
- monday.com
- Stripe
Patterns used
- Search before create
- Two-branch upsert
- Write the invoice back
Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy
Have something shaped like this?
If any part of the above resembles a problem you are living with, a short call is the fastest way to find out whether it is the same problem underneath.
What happens on the call
- 15 minutes, no deck
- We map the process on the call
- A written scope, or an honest no