Skip to content
Notis

Find the DPD customer behind each invoice

Send an invoice for processing and get a focused customer match from DPD, without switching between document and customer records.

Trigger

Webhook received

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

Action

List DPD Customers (Filtered)

Lists DPD customers with filters for contact details, purchases, subscriptions, and creation date.

Why this helps

Invoices and customer records live in separate tools, so matching them by hand can interrupt the work you are doing.

  • Find likely customer records using extracted email or name.
  • Keep the invoice context beside the DPD match in a run report.
  • Review uncertain matches before taking any follow-up action.

Setup

Build it in a few focused steps.

  • 1Connect Algodocs and Dpd2 once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3Tell Notis to extract the invoice customer email and name with Algodocs, search DPD customers for likely matches, and report the invoice and match details.
  • 4Pick a Webhook trigger and choose where run reports should go.
  • 5Test it with one real invoice submission and review the result.

Questions about this workflow

What starts this workflow?

An HTTP request to the Notis Webhook starts it. Send the invoice or document reference in the request so Algodocs can process it.

Does this workflow change a DPD customer record?

No. The selected DPD action searches customers. Notis can report likely matches for you to review.

What if the invoice has no email address?

Notis can use the extracted name to search. If the details are too limited to identify a likely match, the report should say that the match is uncertain.

When this happens · Trigger

Do this · Action

Lists DPD customers with filters for contact details, purchases, subscriptions, and creation date.

Supported Triggers and Actions

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

Algodocs triggers

Dpd2 actions

Recurring trigger

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

TriggerScheduled

Get Storefront

Retrieve details about a storefront.

ActionInstant

Webhook trigger

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

TriggerInstant

List DPD Customers (Filtered)

Lists DPD customers with filters for contact details, purchases, subscriptions, and creation date.

ActionInstant

List DPD Purchases

Lists a page of DPD purchase records.

ActionInstant

List Storefronts

Lists storefronts in your DPD account; a complete list is not guaranteed.

ActionInstant

List Subscribers

Lists a page of subscribers for a DPD storefront.

ActionInstant

DPD: Ping API

Check the API status and connectivity.

ActionInstant

Verify DPD IPN Notification

Verifies a DPD notification using supported fields; other parameters cannot be submitted in full.

ActionInstant

Verify Subscriber

Checks a subscriber’s status using their email username or subscriber ID.

ActionInstant

Connect any two apps with Notis in the middle.

Algodocs and Dpd2, or any other combination from 1,600+ 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 Dpd2.