Dropcontact
CRM & salesAPI keycredential probe
Enrich and verify B2B contacts with Dropcontact: start an enrichment for one contact or a batch of 250, read the result, and manage the result webhook.
OCNORA ships 7 typed Dropcontact operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Anything not covered by a typed node reaches https://api.dropcontact.com/v1 through the HTTP node with the same credential.
Operations 7
- Delete Default WebhookRemove the account's default callback URL. Afterwards only requests that carry their own callback trigger a webhook.dropcontact.delete_webhook
- Enrich BatchStart enrichment for up to 250 contacts in one request and return its request id. Each row may only use fields Dropcontact documents.dropcontact.enrich_batch
- Enrich ContactStart enrichment for one contact and return its request id. Dropcontact needs an email address, a LinkedIn URL, or a name together with a company.dropcontact.enrich_contact
- Get CreditsRead how many enrichment credits the account has left. Dropcontact documents this call as consuming none of them.dropcontact.get_credits
- Get EnrichmentRead the result of an earlier enrichment request. Rows Dropcontact has not finished yet come back unchanged when partial results are forced.dropcontact.get_enrichment
- Get Default WebhookRead the account's current default callback URL.dropcontact.get_webhook
- Set Default WebhookSet the account's default callback URL, used by every enrichment request that does not carry its own. Only one default is allowed.dropcontact.set_webhook
Run your first Dropcontact workflow today.
Create a free workspace, add the connection, pick a template or describe the workflow to Build with AI. Workflow Health checks it before it runs.