My new step-by-step program to get you your first automation customer is now live! Results guaranteed. Apply fast: skool.com/makerschool/about. Price increases every 10 members 🙏😤
🎯 Key points for quick navigation: 00:00 *🎬 Introduction and Overview* - Introduction to the video and explanation of the Stripe API for sending and tracking invoices, - Description of the common use case and the importance of understanding the Stripe API. 02:18 *💡 Understanding Payment Intents and Invoices* - Explanation of the difference between payment intents and invoices, - Clarification on how invoices generate payment intents and the importance of tracking these correctly. 05:37 *🔄 Setting Up Automation with ClickUp* - Demonstration of how to set up automation in ClickUp to trigger a webhook, - Detailed walkthrough on configuring ClickUp to send data to a webhook when the status changes to "send invoice". 09:57 *🧩 Creating a Customer and Invoice Items in Stripe* - Steps to create a customer in Stripe using data from ClickUp, - Process of creating an invoice item and assigning it to the customer before generating an invoice. 13:27 *📋 Generating and Finalizing Invoices* - Explanation of the need to create invoice items before generating an invoice, - Detailed steps to finalize the invoice and ensure it is correctly set up for the customer to pay. 17:14 *📧 Viewing and Paying the Invoice* - Overview of the customer experience when receiving and paying an invoice, - Display of the invoice PDF and explanation of the information included in it, such as due date and payment details. 19:08 *💵 Finalizing and Testing Invoice* - Multiplying the amount by 100 to correct the currency, - Saving and exporting the blueprint for future use, - Finalizing the draft invoice with the correct details. 20:04 *🕵️ Watching Payment Intents* - Creating a new scenario to watch for payment intents, - Using Stripe’s “watch payment events” module to track payment completions, - Filtering payments using customer email to update ClickUp tasks accordingly. 21:55 *🛠️ Implementing Customer Search and Task Update* - Retrieving customer details using customer ID from the payment event, - Searching ClickUp for tasks using the customer’s email address, - Updating the task status to "closed" upon successful payment detection. 24:28 *📊 Completing the Workflow* - Ensuring proper mapping of task IDs and status updates in ClickUp, - Testing the entire flow to verify that the task status updates correctly, - Discussing potential extensions of the workflow, such as sending onboarding emails and tracking finances in Google Sheets. 26:05 *🤖 Conclusion and Recommendations* - Summarizing the steps taken to automate invoice sending and payment tracking, - Highlighting the importance of integrating bookkeeping and finance tracking, - Encouraging further automation to enhance project management and customer onboarding processes. Made with HARPA AI
Nick, what happens if the person that pays is different than the email record you have on file? Doesn't that break the automation for the stage = closed update?
You might need to assign the invoice to the customer and just watch for payments to that invoice and mark as paid for the customer it has been billed to regardless of who’s credit card paid for it. It depends on the quirks of the system you want to build looks like.
I would love to know more about how you map out your customers processes. Do you have them document everything and you work off that documentation? Or do you work step by step with them through the process?
@@BenOded-in7um nope didn't find a solution. Did you check the auto-advance setting in the invoice module? Can't remember if it's in the create invoice or create invoice item. For some that worked, but not for me. Maybe it'll be enough for you.
Bro Nick! Any idea how to create the customer with a designated currency through make? Or maybe create a one off invoice that allows to change the currency through make The create invoice module supposedly adapts the default currency of the Created Customer, but through make, this becomes problematic since you cannot set it - is that correct?
Great video as usual, implementing it now. I am desperate to learn and get accepted into your Skool community 🙏 Any idea when you will be allowing access to further students, Regards, Mick.
can you do this in “Make” like when you speak to an ai assistant, it adds a task in google sheets or in notion, and respond with voice like “Task has been added Sir” is that possible?
![[LIVE] : ONE ลุมพินี 87 วันนี้!! คู่เอก "ก้องชัย vs โชคปรีชา"](http://i.ytimg.com/vi/YN6e7HVnekw/mqdefault.jpg)
My new step-by-step program to get you your first automation customer is now live!
Results guaranteed. Apply fast: skool.com/makerschool/about. Price increases every 10 members 🙏😤
🎯 Key points for quick navigation:
00:00 *🎬 Introduction and Overview*
- Introduction to the video and explanation of the Stripe API for sending and tracking invoices,
- Description of the common use case and the importance of understanding the Stripe API.
02:18 *💡 Understanding Payment Intents and Invoices*
- Explanation of the difference between payment intents and invoices,
- Clarification on how invoices generate payment intents and the importance of tracking these correctly.
05:37 *🔄 Setting Up Automation with ClickUp*
- Demonstration of how to set up automation in ClickUp to trigger a webhook,
- Detailed walkthrough on configuring ClickUp to send data to a webhook when the status changes to "send invoice".
09:57 *🧩 Creating a Customer and Invoice Items in Stripe*
- Steps to create a customer in Stripe using data from ClickUp,
- Process of creating an invoice item and assigning it to the customer before generating an invoice.
13:27 *📋 Generating and Finalizing Invoices*
- Explanation of the need to create invoice items before generating an invoice,
- Detailed steps to finalize the invoice and ensure it is correctly set up for the customer to pay.
17:14 *📧 Viewing and Paying the Invoice*
- Overview of the customer experience when receiving and paying an invoice,
- Display of the invoice PDF and explanation of the information included in it, such as due date and payment details.
19:08 *💵 Finalizing and Testing Invoice*
- Multiplying the amount by 100 to correct the currency,
- Saving and exporting the blueprint for future use,
- Finalizing the draft invoice with the correct details.
20:04 *🕵️ Watching Payment Intents*
- Creating a new scenario to watch for payment intents,
- Using Stripe’s “watch payment events” module to track payment completions,
- Filtering payments using customer email to update ClickUp tasks accordingly.
21:55 *🛠️ Implementing Customer Search and Task Update*
- Retrieving customer details using customer ID from the payment event,
- Searching ClickUp for tasks using the customer’s email address,
- Updating the task status to "closed" upon successful payment detection.
24:28 *📊 Completing the Workflow*
- Ensuring proper mapping of task IDs and status updates in ClickUp,
- Testing the entire flow to verify that the task status updates correctly,
- Discussing potential extensions of the workflow, such as sending onboarding emails and tracking finances in Google Sheets.
26:05 *🤖 Conclusion and Recommendations*
- Summarizing the steps taken to automate invoice sending and payment tracking,
- Highlighting the importance of integrating bookkeeping and finance tracking,
- Encouraging further automation to enhance project management and customer onboarding processes.
Made with HARPA AI
Yikes! So glad you went through this process - it's much clearer now. Thanks!
I love the concept and this process for Stripe. Now I just need to work out how to emulate this with Xero.
Nick, what happens if the person that pays is different than the email record you have on file? Doesn't that break the automation for the stage = closed update?
You might need to assign the invoice to the customer and just watch for payments to that invoice and mark as paid for the customer it has been billed to regardless of who’s credit card paid for it.
It depends on the quirks of the system you want to build looks like.
I would love to know more about how you map out your customers processes. Do you have them document everything and you work off that documentation? Or do you work step by step with them through the process?
I can't make the email to be sent for the invoice, even though it is correctly created and finalized. Any ideas why?
I have the same issue, any thoughts? Stripe does not send the email to the email address
@@BenOded-in7um nope didn't find a solution. Did you check the auto-advance setting in the invoice module?
Can't remember if it's in the create invoice or create invoice item.
For some that worked, but not for me. Maybe it'll be enough for you.
@@kailtis the auto-advance setting worked for me.
@@kailtis Holy shit I spent over an hour reading stripes api to try to fix that, saw your comment and boom, it worked. Thank you so much mate.
Bro Nick! Any idea how to create the customer with a designated currency through make? Or maybe create a one off invoice that allows to change the currency through make
The create invoice module supposedly adapts the default currency of the Created Customer, but through make, this becomes problematic since you cannot set it - is that correct?
Thank you! Very valuable
Great video as usual, implementing it now. I am desperate to learn and get accepted into your Skool community 🙏 Any idea when you will be allowing access to further students, Regards, Mick.
how can we make a automation where we want to know whether the email is opened or not
please help
can you do this in “Make” like when you speak to an ai assistant, it adds a task in google sheets or in notion, and respond with voice like “Task has been added Sir” is that possible?
Hey Nick!
Could you also share how you price clients?
Regards!
You could have also used receipt email to update on clickup-- I think you missed that
hey man unrelated question but can you connect multiple email addresses to a module that triggers whenever an email is received to any of them?
You can set up a filter for your matched criteria inside your email client(s) and then forward to a mailhook module inside make
not glowing. matte. not even satin. no gloss. only matte.