Skip to main content

Batch Post

Submits a batch of contact data to Dropcontact for enrichment and returns a request ID for retrieving results.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs​

  • Data - An object containing contact data to submit for enrichment. This should include the data array with contact objects and optional configuration parameters.

Options​

  • API Key - Dropcontact API key for authentication (credential type).

Output​

  • request_id - A unique request ID string used to retrieve enrichment results later using the Batch Result node.

How It Works​

The Batch Post node submits contact data to Dropcontact's batch enrichment API. When executed, the node:

  1. Validates the input data object
  2. Serializes the data to JSON format
  3. Constructs an HTTP POST request to the Dropcontact API endpoint
  4. Adds authentication headers with the API key
  5. Sends the request to https://api.dropcontact.io/batch
  6. Parses the response to extract the request ID
  7. Returns the request ID for use with the Batch Result node

Requirements​

  • A valid Dropcontact account with API access
  • API key configured in credentials
  • Properly formatted contact data matching Dropcontact's requirements
  • At least one of the following data combinations per contact:
    • first_name + last_name + company (or full_name + company)
    • LinkedIn URL
    • Email address

Error Handling​

The node will return specific errors in the following cases:

  • ErrInternal - Failed to create HTTP request or parse response
  • ErrRuntime - Failed to serialize data or send HTTP request
  • ErrInvalidArg - Invalid or missing API key
  • Missing request_id in API response

Usage Notes​

  • You can submit up to 250 contacts per batch request
  • Each contact data must be less than 15 kB
  • The API processes requests asynchronously - use the returned request ID with the Batch Result node to retrieve results
  • Credits are only charged when emails are found or verified
  • Use the Batch Result node to poll for results after submission
  • Consider using the Credits Left node to check remaining credits before large batch operations

Data Format​

The Data input should be structured as an object with a data array containing contact objects:

{
  "data": [
    {
      "first_name": "John",
      "last_name": "Doe",
      "company": "Acme Corp",
      "email": "john@example.com",
      "phone": "+1234567890",
      "website": "https://example.com",
      "linkedin": "https://www.linkedin.com/in/johndoe/"
    },
    {
      "first_name": "Jane",
      "last_name": "Smith",
      "company": "Tech Industries",
      "website": "https://techindustries.com"
    }
  ],
  "siren": true,
  "language": "en"
}

Optional Parameters​

  • siren (boolean) - Retrieve SIREN, NAF codes, VAT, and company address information
  • language (string) - Set to "en" for English responses (defaults to French)
  • custom_callback_url (string) - Optional webhook URL for this specific request

Contact Object Fields​

All fields are optional, but you must provide at least one valid combination:

  • email - Email address to verify and enrich
  • first_name - First name of the contact
  • last_name - Last name of the contact
  • full_name - Full name (alternative to first_name + last_name)
  • phone - Phone number
  • company - Company name
  • website - Company website URL
  • linkedin - Contact's LinkedIn profile URL
  • company_linkedin - Company's LinkedIn page URL
  • siren - French company SIREN number
  • siret - French company SIRET number

Example: Enrich Multiple Contacts​

Flow Setup:

  1. Prepare contact data in a previous node
  2. Use Batch Post to submit for enrichment
  3. Store the request_id in a variable
  4. Wait for processing (30-60 seconds recommended)
  5. Use Batch Result with the request_id to retrieve enriched data

Input Data:

{
  "data": [
    {
      "first_name": "Sarah",
      "last_name": "Johnson",
      "company": "Marketing Solutions Inc",
      "website": "https://marketingsolutions.com"
    },
    {
      "email": "contact@techstartup.io",
      "company": "Tech Startup"
    },
    {
      "linkedin": "https://www.linkedin.com/in/michaelbrown/",
      "company": "Consulting Group"
    }
  ],
  "siren": false,
  "language": "en"
}

Output:

request_id: "abc123def456ghi789jkl"

Example: CRM Contact Enrichment​

This example enriches contacts from a CSV file or CRM export:

  1. Read CSV node - Load contact data from file
  2. Loop node - Iterate through contacts in batches of 250
  3. Object node - Build data object with contact array
  4. Batch Post node - Submit batch for enrichment (stores request_id)
  5. Delay node - Wait 45 seconds for processing
  6. Batch Result node - Retrieve enriched data
  7. Excel node - Save enriched contacts to file

Tips:

  • Process contacts in batches of 250 for optimal performance
  • Add delays between batch submissions to avoid rate limits
  • Store request IDs in a data table for tracking multiple batches
  • Check Credits Left before starting large enrichment operations

Common Errors and Solutions​

Error: "Failed to serialize data"​

Cause: Invalid data format or non-serializable values Solution: Ensure the data object contains only valid JSON-compatible values (strings, numbers, booleans, arrays, objects)

Error: "request_id cannot be found"​

Cause: API response doesn't contain a request ID, usually due to invalid request Solution:

  • Verify your data includes at least one valid contact with required fields
  • Check that you're not exceeding 250 contacts per request
  • Ensure each contact is under 15 kB

Error: "Failed to send request"​

Cause: Network connectivity issues or API endpoint unreachable Solution:

  • Check your internet connection
  • Verify firewall settings allow HTTPS requests to dropcontact.io
  • Retry the request after a brief delay

Error: "ErrInvalidArg" with API key​

Cause: API key credential not configured or invalid Solution:

  • Verify the Dropcontact API Key credential is properly configured in vault
  • Ensure the credential is selected in the node's options
  • Check that your API key is valid and active in your Dropcontact account

Best Practices​

  1. Batch Size: Submit 200-250 contacts per batch for optimal throughput
  2. Error Recovery: Enable Continue On Error and log failed batches for retry
  3. Rate Limiting: Add 1-2 second delays between batch submissions
  4. Credit Management: Check credits before large operations using Credits Left node
  5. Data Quality: Clean and validate contact data before submission to maximize match rates
  6. Request Tracking: Store request IDs with timestamps in a data table for audit trails
  7. Polling Strategy: Wait 30-60 seconds before checking results with Batch Result node