Detect new payments
The workflow checks ERPNext every 3 minutes for new incoming Payment Entries. Payments not linked to a customer are skipped.
LIVE WEBINAR · 18 NOV: Make your SAP Business One ready for Black Friday — live demo 18 November. Save my seat
When a customer's first ERPNext invoice is paid, find the matching HubSpot company and set it and its associated contacts to the Customer lifecycle stage
Apps used in this template
About this template
HubSpot lifecycle stages often stay at an earlier stage long after a customer has paid, because finance data never reaches the CRM. This template checks ERPNext every 3 minutes for new customer Payment Entries, confirms the payment settles a Sales Invoice and is the customer's first, then sets the HubSpot company with the same name and all its associated contacts to Customer.
Key benefits
Inside the flow
Every 3 minutes, the workflow picks up new ERPNext Payment Entries from customers and checks that each settles a Sales Invoice and is the customer's first payment. It then finds the HubSpot company by customer name and sets the company and its associated contacts to the Customer lifecycle stage.
The workflow checks ERPNext every 3 minutes for new incoming Payment Entries. Payments not linked to a customer are skipped.
It retrieves the full payment record, including the invoices it settles. If it does not settle a Sales Invoice, it creates an ERPNext ToDo for review and stops.
It searches ERPNext for an earlier submitted payment from the same customer. If one exists, the flow stops, since the customer is already paying.
It looks up the HubSpot company by the customer's name. If none is found, it creates an ERPNext ToDo so the team can review it.
The company's lifecycle stage in HubSpot is set to Customer.
It retrieves every contact associated with the company and sets each one to Customer. If there are none, the company update still stands.
Lifecycle stages that follow real payments, not pipeline guesses
01
Companies and contacts move to Customer as soon as the first invoice is paid, with no manual updates from sales or finance.
02
Marketing reports can show which campaigns led to paying customers, because lifecycle stages follow real ERPNext payments.
03
Only the first paid invoice triggers the change, which keeps lifecycle stages clean and avoids repeated updates.
04
The company and every associated contact are updated together, so sales, marketing and customer success see the same status.
05
Payments without a Sales Invoice and customers without a matching HubSpot company are logged as ERPNext ToDos.
01
Companies and contacts move to Customer as soon as the first invoice is paid, with no manual updates from sales or finance.
02
Marketing reports can show which campaigns led to paying customers, because lifecycle stages follow real ERPNext payments.
03
Only the first paid invoice triggers the change, which keeps lifecycle stages clean and avoids repeated updates.
04
The company and every associated contact are updated together, so sales, marketing and customer success see the same status.
05
Payments without a Sales Invoice and customers without a matching HubSpot company are logged as ERPNext ToDos.
Keep exploring
Every repetitive process between your ERP, CRM, and business apps has a template. Find yours, customize it, and go live today.
Customize the flow
Every trigger and action this template uses is available in the appse ai builder, so the same flow can be rebuilt with your own routing, thresholds and destinations.
Questions & answers
Everything you need to know about this template before you deploy it.
Discover how appse ai has helped businesses automate processes and achieve growth through our users' success stories.
Start free — no credit card, no setup calls required. Use this template as-is or customize every step inside the appse ai no-code builder and go live today.