Connectors

/

Rillet

/

Tag overdue Rillet customers in Drip
Write
Cross-Connector

Tag overdue Rillet customers in Drip for different emails

For finance and marketing teams who want Drip subscribers at customers with overdue Rillet invoices tagged so automations treat them differently.

Try PopdockAI free
Get a live demo
Tag overdue Rillet customers in Drip
Tag Drip subscribers at Rillet customers with invoices over 15 days late as Overdue.
9 Rillet customers are over 15 days late; 12 Drip subscribers can be tagged. - Largest: Contoso, 9,200 USD, due 2 September - Already tagged: 3, skipped - Not in Drip: 2, skipped Shall I tag the 12 subscribers Overdue?
Rillet
Sample figures. Your results come from your own account.
rillet-get-invoices
rillet-get-customer-emails
drip-get-subscriber
drip-add-subscriber-tag

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Rillet

Rillet
Run it on your own Rillet data.

Connect Rillet, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Overdue customers keep getting promotional email

When a customer falls behind in Rillet, your Drip emails keep treating them like everyone else, promotions and all. Flagging them means pulling overdue invoices, matching emails and tagging each subscriber by hand, so it rarely happens.

Without PopdockAI

  • Pull overdue invoices from Rillet
  • Match each customer to their email addresses
  • Find each subscriber in Drip
  • Tag them one at a time, if anyone has time

With PopdockAI

  • Overdue balances totalled per customer with oldest due date
  • Emails matched to Drip, already tagged or missing people skipped
  • Name, email, amount due and due date shown before tagging
  • The tag applied only after you approve, Rillet never written

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Tag Drip subscribers `{tag}` (default Overdue) when their Rillet customer has an invoice at least `{days-overdue}` days past its due-date (default 1) with amount-due above zero, so Drip automations can treat them differently.

**Step 1: Find overdue customers**

Call `rillet-get-invoices` (Rillet) once. Keep invoices with amount-due above zero whose due-date is at least `{days-overdue}` days before today. Collect the distinct customer-ids with the total amount-due per currency and the oldest due-date.

**Step 2: Carry across to Drip**

Call `rillet-get-customer-emails` (Rillet) once and attach every email for each customer-id. For each email, call `drip-get-subscriber` (Drip) with email set to it. Keep emails that exist in Drip and do not already carry the tag. Skip emails with no Drip record; list them separately.

**Step 3: Confirm**

Show the user: customer name, email, amount-due, oldest due-date, and the tag to apply. Ask for explicit confirmation before writing.

**Step 4: Write**

For each confirmed email, call `drip-add-subscriber-tag` (Drip) once with email and tag set to `{tag}` (or Overdue).

**Step 5: Report**

List tagged, already tagged, not in Drip, and failed, with counts.

**Rules & Guidelines:**

* The only key shared by the two systems is the email address. Rillet emails come from `rillet-get-customer-emails` (one row per address, with its customer-id and email-type); Drip emails come from the email field of `drip-get-subscriber`. Compare them trimmed and lower-cased. Never match on name alone.
* `rillet-get-customer-emails` and `rillet-get-invoices` take no filters. Call each once, keep the result, and match in memory rather than calling them per customer.
* The only tool that may write is `drip-add-subscriber-tag` on Drip, after Step 3. Do not call `drip-add-subscriber` to create missing people, and do not call `drip-unsubscribe-subscriber`, `drip-remove-subscriber-from-all-campaigns` or `drip-start-subscriber-workflow`.
* Never call any Rillet tool whose name starts with rillet-add, rillet-update, rillet-apply, rillet-unapply, rillet-record, rillet-set or rillet-setup. Rillet is read-only in this prompt.
* This prompt does not remove the tag from customers who have since paid. Say so in the report if any tagged subscriber now has no overdue invoice.

**Validation:**

* If nothing is overdue, say so and stop.
* If the user does not confirm, stop and write nothing.

Who it's for

One answer, three teams that use it

Collections

Line email up with collections

Overdue customers carry a tag your automations can use, so they get the right messages.

Tag everyone at Rillet customers more than 30 days overdue as Past due in Drip.

Lifecycle marketers

Keep promotions away from overdue accounts

Use the tag to exclude overdue customers from offers until they are back on track.

Find Rillet customers overdue by 15 days and tag their Drip subscribers Hold promos.

Finance managers

Approve exactly who is flagged

You see each name, amount due and due date before any tag is applied.

Show me which Drip subscribers at overdue Rillet customers like Contoso would be tagged Overdue.

How it works

What PopdockAI does when you ask

You set how many days late counts as overdue and the tag to use, and your AI assistant finds who to tag in Drip. Nothing is tagged until you approve the list.

01

Ask

You set how many days past due counts and the tag to use.

Your AI tool

02

Read

It totals overdue Rillet balances per customer with the oldest due date.

rillet-get-invoices

03

Match

It matches emails to Drip and skips tagged or missing people.

rillet-get-customer-emails
drip-get-subscriber

04

Tag

You approve the list, then the tag is applied in Drip.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Rillet and one secure connection to your AI tool. No code, no exports.

get-data

rillet-get-invoices

Returns customer invoices (number, customer, dates, status, totals, amount due) from Rillet.
get-data

rillet-get-customer-emails

Returns customer email addresses with their type and the customer's location from Rillet.
get-data

drip-get-subscriber

Returns Drip people (subscribers) with name, email, location, tags, status, GDPR consent, lead score and lifetime value. Filter by exact email, email domain, tag, status, country, minimum lead score, minimum lifetime value or date added.
run-action

drip-add-subscriber-tag

Applies a tag to a Drip subscriber identified by email address. Creates the tag if it does not exist.
Read only.Nothing in Rillet Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

Overdue customers tagged for the right messages

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation