DROPCONTACT n8n INTEGRATION: AUTOMATE DROPCONTACT WITH N8N

The Enrich contact action is the core functionality of the Dropcontact n8n integration. It takes an email address and returns enriched professional information about that contact—think of it as your automated research assistant that digs up company details, job titles, LinkedIn profiles, and verified contact data in seconds.

Key parameters for this action:

• Credential to connect with: A dropdown field where you select your Dropcontact API credential. This is required to authenticate your request against the Dropcontact API.
• Resource: Set to "Contact" by default, defining the type of data you're working with. This is required.
• Operation: Set to "Enrich", specifying you want to enrich data rather than perform another operation. This is required.
• Email: A text input field where you provide the email address to enrich. This is required and accepts both static values and dynamic expressions (e.g., pulling the email from a previous node's output).
• Simplify Output (Faster): An optional toggle switch that, when enabled, returns a streamlined response for faster processing. Useful when you only need key data points rather than the full enrichment payload.
• Additional Fields / Options: Expandable sections for adding custom parameters or refining the enrichment operation—optional but useful for advanced configurations.

When to use this action: Perfect for enriching leads in real-time as they enter your funnel, cleaning up existing CRM contacts, or building pre-qualification workflows that route leads based on enriched company data. Combine it with a CRM node like HubSpot to automatically update contact records with fresh professional information.

The FetchRequest contact action allows you to retrieve the results of a previously submitted enrichment request. This is particularly useful when working with asynchronous enrichment workflows or when you need to check the status of batch operations.

Key parameters for this action:

• Credential to connect with: Dropdown selection for your Dropcontact API credential. Required for authentication.
• Resource: Set to "Contact", indicating you're working with contact data. Required.
• Operation: Set to "Fetch Request", specifying you want to retrieve an existing enrichment request's results rather than create a new one. Required.
• Request ID: A text input field accepting the unique identifier of the enrichment request you want to retrieve. This is required and can be a fixed value or an expression pulling the ID from a previous workflow step.

When to use this action: Ideal for workflows where enrichment happens asynchronously—you submit a request, wait for processing, then fetch the completed results. Also useful for building retry logic: if an enrichment isn't ready yet, you can loop back and fetch again after a delay. This action pairs well with the Enrich contact action in scenarios where you need to handle large volumes or manage rate limiting gracefully.