HubSpot Contact Enrichment with Clearbit Workflow

This workflow enriches HubSpot contacts with Clearbit data when contacts are created or updated, validating inputs and logging outcomes. Key nodes include HubSpot Contact Trigger (detects contact events), Validate Trigger Data (checks contact ID), Get Contact Details (fetches HubSpot data), Validate Contact Data (verifies email), Enrich with Clearbit (fetches enrichment), Update HubSpot Contact (updates contact), and Log Success/Skip/Error (logs results). It uses HubSpot and Clearbit APIs.\n\nSetup Requirements: Install n8n from n8n.io or sign up at cloud.n8n.io. Import the JSON into n8n’s workflow editor. Create a HubSpot app at hubspot.com (Developer Account > Integrations > Create App) to get OAuth2 credentials and Developer API key. Get a Clearbit API key from clearbit.com (Dashboard > API). In n8n, configure credentials: HubSpot (OAuth2 and Developer API) and Clearbit (API Key). Set HubSpot Contact Trigger for contact. creation and contact.propertyChange events; find the webhook URL in the node. Register this URL in HubSpot (Settings > Integrations > Webhooks). Handle errors like missing contact ID (400: Contact ID not found) or invalid API key (401: Authentication failed).\n\nTesting and Deployment: Import the JSON into n8n. Create or update a HubSpot contact with an email (e.g., test@example.com). Trigger manually via HubSpot Contact Trigger. Verify Validate Trigger Data extracts contact_id and Get Contact Details fetches properties. Confirm Validate Contact Data checks email and Enrich with Clearbit retrieves data. Check Update HubSpot Contact updates fields (e.g., city, job title) and Log Success records outcomes. Test with an invalid email to trigger Log Skip (no_email) or Log Validation Error (404: Contact not found). Monitor for errors like Clearbit rate limits (429: Rate limit exceeded) or HubSpot permission issues (403: Forbidden). If enrichment fails, verify API keys and email format. Activate the workflow in n8n and ensure HubSpot’s webhook is live. Deploy for automated contact enrichment and error logging.