crm webhook trigger and update groundhogg deliverable and update groundhogg not deliverable
Configured with HTTP Request, Switch, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Transform
- Trigger
- Web / API
- Routing
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 |
|---|---|---|---|
| Set Address Fields | Transform | Edit Fields | See node parameters |
| CRM Webhook Trigger | Trigger | Webhook | See node parameters |
| Update Groundhogg - Deliverable | Web / API | HTTP Request | POST |
| Update Groundhogg - NOT Deliverable | Web / API | HTTP Request | POST |
| Address Verification | Web / API | HTTP Request | POST |
| Switch | Routing | Switch | 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
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Purpose
Purpose
To verify the mailing address for new contacts in Groundhogg CRM.
Whenever I add a new contact to Groundhogg CRM, I run this automation to ensure I have a valid mailing address. It also helps me check for misspellings if the contact address was manually entered.
Quick Video Overview:
https://www.youtube.com/watch?v=nrV0P0Yz8FI
Sticky Note1
Update Groundhogg CRM to indicate if the address is deliverable.
Possible Options:
- Add Tag
- Add Note
- Start Automation
- Update a Field
For Deliverable Addresses - I apply a tag that the address was verified.
For Non Deliverable Addresses - I apply a tag, which triggers an automation for my team to manually verify the address. You could also trigger an automation to reach out to the contact to verify their address.
Sticky Note2
Receive a webhook from your CRM with the contact address fields
Sticky Note3
- Create an Account a LOB.com
- Create API Key (https://help.lob.com/account-management/api-keys)
- Update Node with your Credentials (Basic Auth)
crm webhook trigger and update groundhogg deliverable and update groundhogg not deliverable
crm webhook trigger and update groundhogg deliverable and update groundhogg not deliverable
Purpose and structure
This folder contains the crm webhook trigger and update groundhogg deliverable and update groundhogg not deliverable workflow. Its executable nodes use httpRequest, set, switch, webhook. 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
CRM Webhook Trigger
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/Http/0485_HTTP_Stickynote_Create_Webhook.json MIT; preserve source notices.