piepdrive-test
Configured with HTTP Request, Markdown, Open Ai, Pipedrive, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Integration
- Code
- Web / API
- Transform
- Messaging
- AI & models
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Pipedrive Trigger - An Organization is created | Trigger | Pipedrive Trigger | See node parameters |
| Pipedrive - Create a Note with OpenAI output | Integration | Pipedrive | note |
| Code - Markdown to Slack Markdown | Code | Code | See node parameters |
| Scrapingbee - Get Organization's URL content | Web / API | HTTP Request | See node parameters |
| HTML To Markdown | Transform | Markdown | See node parameters |
| Slack - Notify | Messaging | Slack | See node parameters |
| OpenAI - Message GPT-4o with Scraped Data | AI & models | Open Ai | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
openAiApipipedriveApislackOAuth2Api
Workflow notes
Enrich Pipedrive's Organization Data with GPT-4o When an Organization is Created in Pipedrive
Enrich Pipedrive's Organization Data with GPT-4o When an Organization is Created in Pipedrive
This workflow enriches a Pipedrive organization's data by adding a note to the organization object in Pipedrive. It assumes there is a custom "website" field in your Pipedrive setup, as data will be scraped from this website to generate a note using OpenAI.
⚠️ Disclaimer
These workflows use a scraping API. Before using it, ensure you comply with the regulations regarding web scraping in your country or state.
Important Notes
-
The OpenAI model used is GPT-4o, chosen for its large input token context capacity. However, it is also the most expensive option, you should take cost into consideration.
-
The system prompt in the OpenAI Node generates output with relevant information, but feel free to improve or modify it according to your needs.
How It Works
Node 1: Pipedrive Trigger - An Organization is Created
This is the trigger of the workflow. When an organization object is created in Pipedrive, this node is triggered and retrieves the data. Make sure you have a "website" custom field (the name of the field in the n8n node will appear as a random ID and not with the Pipedrive custom field name).
Node 2: ScrapingBee - Get Organization's Website's Homepage Content
This node scrapes the content from the URL of the website associated with the Pipedrive Organization created in Node 1. The workflow uses the ScrapingBee API, but you can use any preferred API or simply the HTTP request node in n8n.
Node 3: OpenAI - Message GPT-4o with Scraped Data
This node sends HTML-scraped data from the previous node to the OpenAI GPT-4 model. The system prompt instructs the model to extract company data, such as products or services offered and competitors (if known by the model), and format it as HTML for optimal use in a Pipedrive Note.
Node 4: Pipedrive - Create a Note with OpenAI Output
This node adds a Note to the Organization created in Pipedrive using the OpenAI node output. The Note will include the company description, target market, selling products, and competitors (if GPT-4 was able to determine them).
Node 5 & 6: HTML To Markdown & Code - Markdown to Slack Markdown
These two nodes format the HTML output to Slack Markdown.
The Note created in Pipedrive is in HTML format, as specified by the System Prompt of the OpenAI Node. To send it to Slack, it needs to be converted to Markdown and then to Slack-specific Markdown.
Node 7: Slack - Notify
This node sends a message in Slack containing the Pipedrive Organization Note created with this workflow.
piepdrive-test
piepdrive-test
Purpose and structure
This folder contains the piepdrive-test workflow. Its executable nodes use code, httpRequest, markdown, openAi, pipedrive, pipedriveTrigger, slack. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Pipedrive Trigger - An Organization is created
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/1435_Code_Slack_Automation_Webhook.json MIT; preserve source notices.