Can Lyro issue a refund or change an order in DPD?

No. The connected actions read and verify only - Get Storefront, List DPD Purchases, List Subscribers, Verify Subscriber - with nothing that creates, edits, or refunds a purchase. Lyro confirms what the record says and hands the change to a human agent with that context attached.

We run several storefronts on one DPD account. Can Lyro tell them apart?

Yes. List Storefronts returns every storefront on the account and Get Storefront returns one storefront's configuration, including its currency, subdomain, and contact details, so a lookup is scoped to the store a customer actually bought from.

What does Lyro need in order to identify a subscriber?

Verify Subscriber accepts either the subscriber's username, which is their email, or their subscriber ID, so the check works from what a customer can tell you in chat. If neither matches, List Subscribers narrows the search within a single storefront.

How is this different from piping DPD's IPN into Zapier?

An IPN pipeline runs one predefined workflow per event. Lyro calls DPD actions while the conversation is still open - verifying the notification, then pulling that buyer's purchase history and subscription status - and picks the lookups the question actually needs.

Dpd2 MCP integration

Finds buyers by email, confirms purchases and subscription status, and validates IPN callbacks without an agent opening the dashboard.

Connect Dpd2 See all integrations

8actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get storefront
Lyro fetches full details about a specific DPD storefront by ID. Support teams view storefront config and status without accessing backend systems.
List dpd customers (filtered)
Lyro queries your customer base with advanced filtering options. Sales teams segment prospects and identify repeat buyers on the fly.
Verify subscriber
Lyro confirms whether a customer has an active storefront subscription. Teams avoid wasted follow-up on lapsed accounts.

See all 8 actions

How businesses use Dpd2 + Lyro

Each card is one request a support team gets, and the Dpd2 actions Lyro runs to close it.

Match the person in chat to a real buyer record
Lyro filters DPD customers by email, name, product purchased, newsletter status, or signup date, so the conversation is tied to an actual account before anything else is answered.
List DPD Customers (Filtered)List DPD PurchasesGet Storefront
Confirm what a customer bought and when
Lyro pulls purchase records with date filters and reads them against the storefront they came from, so an order or missing-download question is settled from the record itself.
List DPD PurchasesGet StorefrontList Storefronts
Check whether a subscription is still active
Lyro verifies a subscriber by email or subscriber ID and lists the subscribers on a storefront, so a renewal or lost-access question is answered from current status rather than a guess.
Verify SubscriberList SubscribersList DPD Customers (Filtered)
Validate a purchase notification before acting on it
When DPD posts an IPN to your endpoint, Lyro replays the posted parameters back to DPD to confirm the callback is genuine and pings the API when connectivity itself is in question.
Verify DPD IPN NotificationDPD: Ping APIList DPD Purchases

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Dpd2 actions it has and picks the ones a request needs.

01
Connect Dpd2
Authorize the Dpd2 account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Dpd2 actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Dpd2 · Lyro

Everything else about Dpd2

Setup, permissions, and the limits of what Lyro can do inside Dpd2.

No. The connected actions read and verify only - Get Storefront, List DPD Purchases, List Subscribers, Verify Subscriber - with nothing that creates, edits, or refunds a purchase. Lyro confirms what the record says and hands the change to a human agent with that context attached.

Every action available in Dpd2

All 8 actions your agent can call on Dpd2, straight from the live MCP connection.

Get storefront
Retrieves detailed information about a specific DPD storefront by its ID.
List dpd customers (filtered)
List customers in your DPD account with advanced filtering.
List dpd purchases
List all purchases made through your DPD account.
List storefronts
List all storefronts in your DPD account.
List subscribers
List subscribers for a given storefront.
Dpd: ping API
Ping the API to check its status.
Verify dpd ipn notification
Verify a POST from the URL integration (IPN/webhook).
Verify subscriber
Verify a subscriber's subscription status.