Create and approve Xero invoices from Pipedrive Closed Won deals with Slack
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 21 nodes and runs on Pipedrive events. Along the way it connects Xero, Slack and Pipedrive. It also calls api.xero.com over HTTP.
How it runs
Trigger: On Pipedrive events.
- If: checks a condition and branches into true / false
- Configure Workflow Settings (Edit Fields (Set)): sets 7 fields: xeroOrganizationId, closedWonStageId, salesAccountCode…
- Retrieve Pipedrive Person (Pipedrive): get (person)
- Prepare Contact Data (Edit Fields (Set)): sets 7 fields: contactName, contactEmail, dealId…
- Search Xero Contact (Xero): get many (contact)
- If: checks a condition and branches into true / false
- Set Existing Contact ID (Edit Fields (Set)): sets 1 field: contactId
- Create New Xero Contact (Xero): work with contact
- Get Pipedrive Deal Products (Pipedrive): get many (deal product)
- Set New Contact ID (Edit Fields (Set)): sets 1 field: contactId
…plus 10 more steps. See the full node list below.
Services it uses
HTTP calls to: api.xero.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- If
n8n-nodes-base.if - Xero
n8n-nodes-base.xero - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Slack
n8n-nodes-base.slack - HTTP Request
n8n-nodes-base.httpRequest - Pipedrive
n8n-nodes-base.pipedrive - Pipedrive Trigger
n8n-nodes-base.pipedriveTrigger
From the author
Quick overview This workflow triggers when a Pipedrive deal is moved into the Closed Won stage, creates a matching draft invoice in Xero, and posts it to Slack for approval before authorising and emailing the invoice to the customer. How it works 1. Triggers…