Skip to content
Notis

Bring completed enrichment results back from a request signal

When your Ably-connected service forwards a completion signal with a Dropcontact request ID, Notis can retrieve the finished contact data for review.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Retrieve Enrichment Results

Retrieve contact enrichment results for a submitted request.

Why this helps

Enrichment completes asynchronously, so results can sit waiting while you search for the right request ID and fetch them manually.

  • Fetch completed enrichment data using the request ID in the webhook payload.
  • Reduce manual checking for completed asynchronous jobs.
  • Review returned contact data alongside the Ably signal that initiated the lookup.

Setup

Build it in a few focused steps.

  • 1Connect Ably and Dropcontact once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3Tell Notis to read the Dropcontact request ID from each incoming webhook request and retrieve that request's completed enrichment results.
  • 4Pick the webhook trigger, choose where run reports go, and have your Ably-connected service send the completion signal to Notis.
  • 5Test with one real completed request ID and review the retrieved results.

Questions about this workflow

Will Ably automatically receive a Dropcontact completion event?

Not from the capabilities described here. Your connected service needs to forward a completion signal containing the request ID to the Notis webhook.

What does Retrieve Enrichment Results need?

It needs the request ID returned when enrichment was initiated. Include that ID in the webhook request.

Can this retrieve results before enrichment finishes?

It is intended for completed enrichment requests. Forward the signal after completion so Notis can retrieve the finished data.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Ably to Dropcontact. A trigger fires from one place; an action lands in another.

Ably triggers

Dropcontact actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Webhook Subscription

Creates a subscription for automatic enrichment completion notifications.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

List Webhook Subscriptions

View configured webhook subscriptions.

ActionInstant

Delete Webhook Subscription

Deletes a webhook subscription and stops notifications; it can instead be paused.

ActionInstant

Retrieve Enrichment Results

Retrieve contact enrichment results for a submitted request.

ActionInstant

Initiate Contact Enrichment

ActionInstant

List Webhook Subscriptions V2

Lists the account’s configured webhook subscriptions.

ActionInstant

Update Webhook Subscription

ActionInstant

Connect any two apps with Notis in the middle.

Ably and Dropcontact, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Dropcontact.