Daily Stripe Charges to Pipedrive Notes Sync
Overview
This workflow automatically syncs successful Stripe charges to Pipedrive by creating notes on the corresponding organization records. It runs daily at 8 AM, fetching only new charges since the last execution, and enriches them with customer and organization data from both Stripe and Pipedrive. This is particularly useful for sales teams who want to keep their CRM updated with payment activity without manual data entry.
Workflow Steps
-
Every day at 8 am (Cron Trigger) — Runs the workflow daily at 8:00 AM. No authentication required.
-
Get last execution timestamp (Function Item Node) — Tracks the last time the workflow ran using n8n's static data feature. On first run, it sets the timestamp to the current time. This ensures only new charges are fetched on subsequent runs. No authentication required.
-
Search for charges in Stripe (HTTP Request Node) — Calls the Stripe API endpoint
https://api.stripe.com/v1/charges/searchwith a query parameter to find charges created after the last execution timestamp with status "succeeded". Uses Stripe API Key authentication (predefined credential type:stripeApi). -
Split array of charges to items (Item Lists Node) — Splits the
dataarray from the Stripe response into individual items so each charge can be processed separately. No authentication required. -
Get customers (Stripe Node) — For each charge, fetches the corresponding customer details from Stripe using the
customerresource andgetAlloperation. Uses Stripe API Key authentication (predefined credential type:stripeApi). -
Rename fields and keep only needed fields (Set Node) — Renames the Stripe customer fields: maps
nametocustomerNameandidtocustomerId. ThekeepOnlySetoption removes all other fields, keeping only these two. No authentication required. -
Add customer name to charge data (Merge Node) — Merges the charge data (from step 4) with the customer data (from step 6) using a key-based merge. It matches the charge's
customerfield with the customer'scustomerIdfield. No authentication required. -
Search organisation (Pipedrive Node) — Searches Pipedrive for an organization matching the customer name using the
organizationresource andsearchoperation. Uses Pipedrive API Key authentication (predefined credential type:pipedriveApi). -
Add organisation Information to charge data (Merge Node) — Merges the charge+customer data with the Pipedrive organization data using index-based merge (inner join). This combines all information into a single data set. No authentication required.
-
Create note with charge information (Pipedrive Node) — Creates a note in Pipedrive on the matched organization. The note content is formatted as
"{{description}}: {{amount / 100}} {{currency}}"(e.g., "Subscription payment: 29.99 USD"). Theorg_idis set to the organization's ID from the search results. Uses Pipedrive API Key authentication. -
Set new last execution timestamp (Function Item Node) — Updates the static data with the current execution timestamp so the next run only fetches charges created after this run. The
executeOnceoption ensures this runs only once even if multiple items are processed. No authentication required.
Setup Instructions
Prerequisites
- A Stripe account with API access
- A Pipedrive account with API access
Credentials Setup
- Stripe API Key: In your Stripe dashboard, go to Developers > API keys and copy your secret key (sk_live_... or sk_test_...). In n8n, create a new Stripe credential and paste the key.
- Pipedrive API Key: In Pipedrive, go to Settings > Personal preferences > API and copy your personal API token. In n8n, create a new Pipedrive credential and paste the token.
Workflow Configuration
- The workflow is pre-configured to run daily at 8 AM. You can change the trigger time in the Cron node.
- The note format can be customized in the "Create note with charge information" node by editing the
contentfield. - The charge search query filters for "succeeded" status. You can modify this in the HTTP Request node's query parameters.
Use Cases and Variations
Primary Use Case
- Sales teams keeping Pipedrive CRM updated with payment activity from Stripe
- Account managers tracking which organizations have made recent payments
- Finance teams automating note creation for audit trails
Possible Adaptations
- Change the trigger: Replace the Cron trigger with a webhook to run in real-time when a charge is created
- Add more data: Include charge metadata, invoice links, or payment method details in the note
- Different CRM: Replace Pipedrive nodes with HubSpot, Salesforce, or other CRM nodes
- Filter charges: Modify the Stripe query to filter by amount, currency, or specific products
- Add notifications: Insert a Slack or email node to alert the team when large payments are processed
- Bidirectional sync: Add logic to update Stripe metadata with Pipedrive organization IDs for cross-referencing
Workflow JSON
{
"meta": {
"instanceId": "8c8c5237b8e37b006a7adce87f4369350c58e41f3ca9de16196d3197f69eabcd"
},
"nodes": [
{
"id": "28349bfd-f68e-4479-9508-28d408033d09",
"name": "Get customers",
"type": "n8n-nodes-base.stripe",
"position": [
5360,
1100
],
"parameters": {
"filters": {},
"resource": "customer",
"operation": "getAll",
"returnAll": true
},
"credentials": {
"stripeApi": {
"id": "26",
"name": "Stripe account"
}
},
"typeVersion": 1
},
{
"id": "3f3d2389-e9ab-4140-8b04-f0a07003cecc",
"name": "Rename fields and keep only needed fields",
"type": "n8n-nodes-base.set",
"position": [
5560,
1100
],
"parameters": {
"values": {
"string": [
{
"name": "customerName",
"value": "={{ $json[\"name\"] }}"
},
{
"name": "customerId",
"value": "={{ $json[\"id\"] }}"
}
]
},
"options": {},
"keepOnlySet": true
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
AI-Powered Competitor Price RAG Pipeline with Logging
Overview This workflow implements a Retrieval-Augmented Generation (RAG) pipeline for processing and analyzing competitor pricing data. It is triggered via a webhook (e.g., by an external scraper), splits incoming text into chunks, generates embeddings using OpenAI, stores them in a Supabase vector store, and then allows an Anthropic-powered AI agent to query that context. Results are appended to a Google Sheet for record-keeping, and any errors trigger a Slack alert to a designated channel. This setup is ideal for teams that need to automate the ingestion of structured or unstructured competitor data, enable natural language queries against that data, and maintain an audit log—all without manual intervention. Node-by-Node Breakdown Sticky Note — A visual note in the editor (not executed). Webhook Trigger (No auth) — Listens for incoming POST requests at the path . This is the entry point; an external service (e.g., a custom scraper) should send data here. Text Splitter (No auth) — Splits the incoming text into chunks of 400 characters with 40 character overlap. This ensures the embeddings are meaningful and context windows are manageable. Embeddings (API Key auth — OpenAI) — Uses the model to convert each text chunk into a vector embedding. Requires an OpenAI API key. Supabase Insert (API Key auth — Supabase) — Inserts the generated embeddings into the Supabase vector store under the index . This stores the data for future retrieval. Supabase Query (API Key auth — Supabase) — Queries the same Supabase vector index to retrieve relevant chunks based on a question or input from the agent. Vector Tool (No auth) — Wraps the Supabase query as a tool that the AI agent can call to fetch contextual data. Window Memory (No auth) — Provides conversational memory (buffer window) so the agent can maintain context across multiple interactions. Chat Model (API Key auth — Anthropic) — The language model that powers the AI agent. Uses Anthropic’s Claude model (selected via credentials). Requires an Anthropic API key. RAG Agent (No auth) — The core AI agent that receives the incoming data, uses the vector tool to retrieve relevant context, and generates a response using the chat model. The system message is set to "You are an assistant for Competitor Price Scraper". Append Sheet (OAuth2 — Google Sheets) — Appends the agent’s response (from the node) to a Google Sheet named . You must specify the Google Sheet ID and sheet name in the node parameters. Slack Alert (OAuth2 — Slack) — Triggered only on error from the RAG Agent. Sends a message to the channel with the error details. Setup Instructions Accounts & Credentials – You will need: - An OpenAI account (for embeddings). Create an API key and add it in n8n as an OpenAI credential. - An Anthropic account (for the chat model). Create an API key and add it as an Anthropic credential. - A Supabase project. Enable the pgvector extension, create a table for embeddings, and get the Supabase URL + anon/public API key. Add these as a Supabase credential in n8n. - A Google Cloud project with the Sheets API enabled. Generate OAuth2 credentials (or use a service account) and add them as a Google Sheets OAuth2 credential in n8n. - A Slack workspace. Create a Slack app with chat:write permission and install it to your workspace. Add the bot token as a Slack OAuth2 credential in n8n. Configure the Webhook – The webhook path is . You can change this as needed. Expose this endpoint (e.g., via n8n’s public URL or a tunnel) so your scraper can POST data to it. Set the Google Sheet ID and sheet name – In the Append Sheet node, replace with the actual ID of your Google Sheet and ensure the sheet is named (or update the parameter). Adjust Slack Channel – In the Slack Alert node, set the channel name (default ) to one that exists in your Slack workspace. Test the workflow – Send a sample POST request with some competitor price text to the webhook URL. Check the Google Sheet for logged responses and test error handling by sending malformed data. Use Cases & Variations Competitive Intelligence – Automate the ingestion of price lists, product descriptions, or news articles from competitors. Use the AI agent to answer questions like “Which competitor has the lowest price on product X?”. Document Q&A – Adapt this pipeline for any document type (PDFs, support tickets, internal memos). Replace the webhook with a file trigger and use the same RAG flow. Multi-Source Ingestion – Add an HTTP Request node before the Text Splitter to fetch data from an API or RSS feed instead of relying on a webhook. Custom Output – Instead of a Google Sheet, send the agent’s response via email, SMS, or directly into a CRM. Scheduled Runs – Swap the Webhook Trigger for a Schedule Trigger to run the ingestion on a regular basis (e.g., daily).
Extract Google Maps Business Leads via Dumpling AI to Google Sheets
Overview This workflow automates the extraction of business listings from Google Maps using Dumpling AI's search-maps API and logs the results into a structured Google Sheet. It's ideal for lead generation, market research, or competitive analysis — allowing you to quickly gather data like business names, ratings, addresses, phone numbers, websites, and booking links without manual browsing. Workflow Steps Trigger: Manual Test Run (Manual Trigger) — Starts the workflow on demand for testing. No authentication required. Search Google Maps via Dumpling AI (HTTP Request) — Sends a POST request to with a JSON body containing the search query (e.g., ) and language. Authentication uses Header Auth — you must provide a Dumpling AI API key as a header (configured in n8n credentials). The response returns an array of places with details like title, rating, address, phone, website, price level, and booking links. Split Places List for Processing (Split Out) — Splits the array from the HTTP response into individual items so each place can be processed separately. No authentication needed. Save Results to Google Sheet (Place Info) (Google Sheets) — Appends each place's data (name, address, rating, price level, type, website, phone, position, booking link) to a specified sheet in a Google Sheets document. Uses OAuth2 authentication (Google account). The sheet name is set to "Google Maps" and the document ID points to a spreadsheet named "Places". Setup Instructions Dumpling AI Account: Sign up at dumplingai.com and obtain an API key. In n8n, create a new Header Auth credential with the key name (e.g., ) and value . Google Sheets: Create a Google Sheet (or use the one referenced in the workflow). In n8n, create a Google Sheets OAuth2 credential by connecting your Google account. Ensure the sheet has a tab named "Google Maps" (or update the sheet name in the node). Customize Query: Edit the of the HTTP Request node to change the search query (e.g., ) or language. Run: Click "Execute Workflow" to test. The first run will prompt you to authorize Google Sheets access. Use Cases & Variations Lead Generation: Replace the query with industry-specific terms (e.g., "dentists in Los Angeles") to build a targeted prospect list. Competitor Analysis: Search for competitors in a niche and analyze their ratings, price levels, and online presence. Real Estate / Local Business Research: Extract data for multiple locations by chaining queries or using a loop. Automation: Replace the Manual Trigger with a Schedule Trigger to run daily/weekly, and add a Set node to dynamically pass queries from a spreadsheet or webhook. Enrichment: Add nodes to clean data, send notifications (Slack/Email), or integrate with a CRM like HubSpot.
Auto-Qualify Google Sheets Leads with OpenAI GPT-4
Overview This workflow automatically qualifies new leads submitted via Google Forms (or directly entered) into a Google Sheet. Using OpenAI's GPT-4, it evaluates each lead against custom criteria (e.g., decision-maker role, team size, email domain) and updates the sheet with a qualification rating and explanation. This saves manual review time and ensures consistent lead scoring for sales teams or community managers. Node-by-Node Breakdown Check for new entries (Google Sheets Trigger – OAuth2) - Listens for new rows added to a specific Google Sheet (connected to a Google Form or standalone). - Configured to poll every minute (adjustable). - Requires: A Google Sheet document ID and sheet name. Qualify leads with GPT (OpenAI – API Key auth) - Uses the chat model. - A system message defines qualification rules (decision-maker, team size, corporate email). - A user message injects the lead's name, email, business area, and team size from the trigger output. - Temperature set to 0.3 for consistent, deterministic responses. - Instructed to reply with a JSON object: . Extract JSON reply (Set Node – no auth) - Parses the from OpenAI's response using . - Stores the resulting object in a new field for downstream nodes. Merge (Merge Node – no auth) - Combines the original lead data (from the trigger) with the parsed GPT reply. - Uses “Combine” mode with “Merge by position” to join the two inputs horizontally. - Input 0 (from trigger) holds the row data; Input 1 (from Extract JSON reply) holds the GPT rating. Update lead status (Google Sheets – OAuth2) - Updates the same Google Sheet with the GPT's rating and explanation. - Matches rows by the column (to avoid updating the wrong row). - Writes the rating into a column (and optionally the explanation if you extend the schema). Setup Instructions Google Cloud / Sheets API - Create a Google Cloud project, enable the Google Sheets API, and create OAuth2 credentials (Desktop app or Web application). - In n8n, add a new Google Sheets credential (OAuth2) using your client ID and secret. OpenAI API Key - Sign up at OpenAI and create an API key. - In n8n, add a new OpenAI credential with your API key. Google Sheet - Use the provided template or create your own with columns: Timestamp, Email Address, Your name, Your business area, Your team size, Rating. - If using Google Forms, submissions will automatically populate the sheet. Configure the workflow - After importing, select each Google Sheets node and choose your credential and the correct sheet/document. - Adjust the polling interval if needed (default: every minute). - Modify the GPT system message to fit your own lead qualification criteria. Use Cases & Adaptations Sales lead scoring: Replace the criteria with your ICP (ideal customer profile) – e.g., industry, company size, budget. Community membership approval: Automatically accept or reject join requests based on responses. Event registration filtering: Qualify attendees for VIP access or follow-up. Extend output: Store the explanation in a separate column by adding it to the Update node's column mapping. Add notifications: Insert a Slack or email node after the Merge to alert your team when a high-quality lead is detected. Use a different model: Switch to for lower cost or for faster responses. This template is a starting point – tweak the prompt, polling frequency, and output columns to match your exact process.