Back to Catalog

Enrich new accounts in Pipedrive using Datagma API

Lucas PerretLucas Perret
841 views
2/3/2026
Official Page

This workflow enriches new accounts in Pipedrive using Datagma API by adding data about ICP (ideal customer profile). Instead of Pipedrive, you can use any other CRM. In this example, ideal buyers are heads of sales/business development.

Prerequisites

How it works

  1. Pipedrive trigger node starts the workflow when a new company is created.
  2. HTTP Request node queries data from Datagma.
  3. Pipedrive node updates Pipedrive contact with new data from Datagma.
  4. The Item Lists node simplifies returned data from Datagma that contain lists (arrays), enabling you to easily modify the structure for further processing without the need to use Function nodes and write custom JavaScript.
  5. IF node identifies if the lead corresponds ICP.
  6. HTTP Request node searches for emails in Datagma.
  7. Set node prepares data for further merging.
  8. Merge node combines data from multiple streams.
  9. Pipedrive node adds a new person in Pipedrive.

Enrich New Accounts in Pipedrive using Datagma API

This n8n workflow automates the process of enriching new organization accounts created in Pipedrive with additional data from an external API (likely Datagma, given the directory name, though the JSON itself only shows a generic HTTP Request). It then updates the Pipedrive organization with the enriched information.

What it does

  1. Monitors Pipedrive for New Organizations: The workflow is triggered whenever a new organization is added to Pipedrive.
  2. Checks for Existing Website Information: It verifies if the newly created organization already has a website URL associated with it.
  3. Enriches Data (if website exists): If a website URL is present, it makes an HTTP request to an external API (e.g., Datagma) to fetch additional company information based on the website.
  4. Updates Pipedrive Organization: The workflow then updates the corresponding organization in Pipedrive with the data received from the external API.
  5. Handles Missing Website: If no website URL is found for the new organization, the workflow does nothing for that specific item.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • Pipedrive Account: An active Pipedrive account with API access.
  • Pipedrive Credentials: Pipedrive API key configured as an n8n credential.
  • Datagma API Key (or similar data enrichment API): Access to a data enrichment API (e.g., Datagma) and its API key. This will need to be configured within the HTTP Request node.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click on "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Paste the workflow JSON or upload the file.
  2. Configure Pipedrive Credentials:
    • Locate the "Pipedrive Trigger" node and the "Pipedrive" node.
    • Click on each Pipedrive node and select or create your Pipedrive API credential.
  3. Configure Data Enrichment API (HTTP Request):
    • Locate the "HTTP Request" node.
    • Edit the node:
      • Set the URL to your data enrichment API endpoint (e.g., Datagma's company enrichment endpoint).
      • Configure the Headers or Query Parameters to include your API key and pass the organization's website URL from Pipedrive. You will likely need to use expressions like {{ $json.website }} to dynamically pass the website URL.
      • Adjust the Method (e.g., GET, POST) as required by the API.
  4. Configure Data Mapping (Edit Fields & Pipedrive Update):
    • Locate the "Edit Fields" (Set) node. This node is currently empty but serves as a placeholder to transform or select the data you want to send to Pipedrive from the API response.
    • Locate the "Pipedrive" node (the one after the "Merge" node).
    • Edit this node to map the enriched data from the "Edit Fields" node to the appropriate fields in your Pipedrive organization.
  5. Activate the Workflow: Once all credentials and configurations are set, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.

The workflow will now automatically run whenever a new organization is created in Pipedrive, enriching its data and updating it accordingly.

Related Templates

Automated YouTube video uploads with 12h interval scheduling in JST

This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. ⚙️ Workflow Logic Manual Trigger — Starts the workflow manually. List Video Files — Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/单词卡/A1-A2). Sort and Generate Items — Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) — Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each video’s scheduled time by order × 12 hours. Converts JST back to UTC for YouTube’s publishAt field. Split in Batches (1 per video) — Iterates over each video item. Read Video File — Loads the corresponding video from disk. Upload to YouTube (Scheduled) — Uploads the video privately with the computed publishAtUtc. Add to Playlist — Adds the newly uploaded video to the target playlist. 🕒 Highlights Timezone-safe: Pure UTC ↔ JST conversion avoids double-offset errors. Sequential scheduling: Ensures each upload is 12 hours apart to prevent clustering. Customizable: Change SPANHOURS, BUFFERMIN, or directory paths easily. Retry-ready: Each upload and playlist step has retry logic to handle transient errors. 💡 Typical Use Cases Multi-part educational video series (e.g., A1–A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. --- Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)

ZaneBy Zane
226

Detect holiday conflicts & suggest meeting reschedules with Google Calendar and Slack

Who’s it for Remote and distributed teams that schedule across time zones and want to avoid meetings landing on public holidays—PMs, CS/AM teams, and ops leads who own cross-regional calendars. What it does / How it works The workflow checks next week’s Google Calendar events, compares event dates against public holidays for selected country codes, and produces a single Slack digest with any conflicts plus suggested alternative dates. Core steps: Workflow Configuration (Set) → Fetch Public Holidays (via a public holiday API such as Calendarific/Nager.Date) → Get Next Week Calendar Events (Google Calendar) → Detect Holiday Conflicts (compare dates) → Generate Reschedule Suggestions (find nearest business day that isn’t a holiday/weekend) → Format Slack Digest → Post Slack Digest. How to set up Open Workflow Configuration (Set) and edit: countryCodes, calendarId, slackChannel, nextWeekStart, nextWeekEnd. Connect your own Google Calendar and Slack credentials in n8n (no hardcoded keys). (Optional) Adjust the Trigger to run daily or only on Mondays. Requirements n8n (Cloud or self-hosted) Google Calendar read access to the target calendar Slack app with permission to post to the chosen channel A public-holiday API (no secrets needed for Nager.Date; Calendarific requires an API key) How to customize the workflow Time window: Change nextWeekStart/End to scan a different period. Holiday sources: Add or swap APIs; merge multiple regions. Suggestion logic: Tweak the look-ahead window or rules (e.g., skip Fridays). Output: Post per-calendar messages, DM owners, or create tentative reschedule events automatically.

Takuya OjimaBy Takuya Ojima
70

Generate event speaker recommendations with Claude AI and Google Sheets

Simplify event planning with this automated n8n workflow. Triggered by incoming requests, it fetches speaker and audience data from Google Sheets, analyzes profiles and preferences, and generates optimized session recommendations. The workflow delivers formatted voice responses and updates tracking data, ensuring organizers receive real-time, tailored suggestions. 🎙️📊 Key Features Real-time analysis of speaker and audience data for personalized recommendations. Generates optimized session lineups based on profiles and preferences. Delivers responses via voice agent for a seamless experience. Logs maintain a detailed recommendation history in Google Sheets. Workflow Process The Webhook Trigger node initiates the workflow upon receiving voice agent or external system requests. Parse Voice Request processes incoming voice data into actionable parameters. Fetch Database retrieves speaker ratings, past sessions, and audience ratings from Google Sheets. Calculate & Analyze combines voice request data with speaker profiles and audience insights for comprehensive matching. AI Optimization Engine analyzes speaker-audience fit and recommends optimal session lineups. Format Recommendations structures the recommendations for voice agent response. Voice Agent Response returns formatted recommendations to the user with natural language summary and structured data. Update Tracking Sheet saves recommendation history and analytics to Google Sheets. If errors occur, the Check for Errors node branches to: Format Error Response prepares an error message. Send Error Response delivers the error notification. Setup Instructions Import the workflow into n8n and configure Google Sheets OAuth2 for data access. Set up the Webhook Trigger with your voice agent or external system's API credentials. Configure the AI Optimization Engine node with a suitable language model (e.g., Anthropic Chat Model). Test the workflow by sending sample voice requests and verifying recommendations. Adjust analysis parameters as needed for specific event requirements. Prerequisites Google Sheets OAuth2 credentials Voice agent API or integration service AI/LLM service for optimization (e.g., Anthropic) Structured speaker and audience data in a Google Sheet Google Sheet Structure: Create a sheet with columns: Speaker Name Rating Past Sessions Audience Rating Preferences Updated At Modification Options Customize the Calculate & Analyze node to include additional matching criteria (e.g., topic expertise). Adjust the AI Optimization Engine to prioritize specific session formats or durations. Modify voice response templates in the Voice Agent Response node with branded phrasing. Integrate with event management tools (e.g., Eventbrite) for live data feeds. Set custom error handling rules in the Check for Errors node. Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
116