[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Chase unpaid Jobber invoices automatically

> Find past due Jobber invoices each week and resend them with a personal note, beyond the two automatic follow-ups. Runs from Claude Code or n8n.

Source: https://cotlet.dev/integrations/jobber-api-mcp-server/chase-unpaid-invoices

Your Jobber invoices go past due on the 28th, the two automatic reminders have already gone out, and now someone has to find the unpaid ones and nudge each client by hand.

Cotlet does it in your own Jobber account with list\_invoices, get\_invoice and send\_invoice, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=jobber) [All Jobber tools](https://cotlet.dev/integrations/jobber-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Jobber do this on its own?

Jobber's Invoice follow-ups, on the Connect plan and up, send up to two reminders per invoice in Past Due status (checked 14 Oct 2026). Each reminder goes out a set number of days after the due date, up to 90, shortly after 8 AM local time, by the same channel as the invoice. Nothing in Jobber reads the balance and history before a reminder, and Zapier has invoice triggers but no action to send an invoice.

## How you do it in Jobber today

1. Open the Invoices list in Jobber and look for the Past Due status, which Jobber sets once an unpaid invoice passes its due date.
2. Open each past due invoice and read the balance and the client's payment history.
3. Choose More Actions, then Email, or Send Text Message, to send the invoice again. The email links to the invoice in client hub.
4. If the client says they paid offline, choose Collect Payment and record it. Otherwise repeat for the next invoice.
5. The list has to be checked again next week, because Jobber's automatic reminders stop after two.

## How to chase unpaid Jobber invoices automatically

Prompt

```
List my past due Jobber invoices over 14 days late. For each one, check the client's last payment, then send the invoice again by email with a short, friendly note. Skip anyone I flagged and tell me the total still owed.
```

1. 01  
### Pull the past due list  
list\_invoices runs with status set to past\_due and due\_before set to your cut-off, so only invoices that are late enough for a human-sounding nudge come back.
2. 02  
### Check each invoice before writing  
get\_invoice shows the balance, the line items and any payments already recorded, so a partly paid invoice is chased for the balance and not the total.
3. 03  
### Skip who you told it to skip  
Invoices on your skip list, or from clients who already got a reminder in the last 7 days, are left out and named in the report.
4. 04  
### Resend with a short note  
send\_invoice sends the invoice again by the channel you choose, with a one-line message written for that client. Every send waits for your OK by default.
5. 05  
### Report the total still owed  
The agent adds up the open balances and lists the invoices it did not touch, so you see the real number and not only what was sent.

### What you get back

Example data

```
Past due over 14 days: 4 invoices, $1,730.00 owed
Resent 3 by email:
- #1042 Maria Santos $480.00 (16 days late)
- #1038 Green Oak Dental $650.00 (21 days late)
- #1035 Tom Becker $400.00 (30 days late)
Skipped 1: #1029 Lena Ortiz $200.00 (reminded 3 days ago)
```

### Other ways to ask

- Every Monday, list invoices more than 30 days past due and draft a firmer note, but send nothing until I confirm.
- Send a text to clients whose past due invoice was first sent by text, and an email to everyone else.
- List the five largest past due balances and tell me who has paid anything before.

## What Jobber allows, and what to know first

- Jobber sends invoice follow-ups only to clients and contacts with "overdue invoice follow-ups" enabled in their communication settings.
- Jobber limits invoice follow-ups to two reminders per invoice, each set up to 90 days after the due date.
- A Jobber invoice emailed from More Actions links to the invoice in client hub; the PDF is attached only if you tick the box.
- Text delivery of invoices is available in the US, Canada and the UK, and the text link expires after 24 hours.
- Jobber marks an invoice Paid when a payment covers the full balance; Close invoice without a payment also sets Paid but leaves the balance owing.

send\_invoice asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [Jobber Help: Invoice Follow-ups](https://help.getjobber.com/hc/en-us/articles/360021573434--Invoice-Follow-ups) · [Jobber Help: Invoice Basics](https://help.getjobber.com/hc/en-us/articles/115009685047-Invoice-Basics) · [Zapier Help: Get started with Jobber on Zapier](https://help.zapier.com/hc/en-us/articles/40859679162381-How-to-get-started-with-Jobber-on-Zapier)

## Call send\_invoice from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/jobber/invoices/inv_20418 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"channel":"email","message":"Hi Maria, a quick reminder that invoice #1042 for $480.00 is past due. You can pay it online from the link below."}'
```

Example response

```
{
"invoice_id": "inv_20418",
"status": "past_due",
"sent_via": "email",
"sent_at": "2026-10-14T09:10:00-04:00"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is jobber\_write → send\_invoice. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/jobber-api-mcp-server.md#automations)

## Jobber tools this automation uses

__Cotlet Jobber tools used to chase unpaid Jobber invoices automatically__
| Tool | Parameters |
| -------------- | ---------------------------------------------- |
| list\_invoices | status, client\_id, due\_before, limit, cursor |
| get\_invoice | invoice\_id |
| send\_invoice | invoice\_id, channel, message |

[All 14 Jobber tools with descriptions](https://cotlet.dev/integrations/jobber-api-mcp-server.md#tools)

## Frequently asked questions

### Does this replace Jobber's automatic invoice follow-ups?

No. Keep them on. This job covers what comes after the second automatic reminder, with a note that fits the client and a check of what was already paid.

### Is it safe to connect Jobber to Cotlet?

Yes. You sign in to Jobber yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Jobber once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Jobber automations

- [Convert approved Jobber quotes to jobs automatically](https://cotlet.dev/integrations/jobber-api-mcp-server/convert-approved-quotes-to-jobs.md)
- [Follow up on unanswered Jobber quotes with AI](https://cotlet.dev/integrations/jobber-api-mcp-server/follow-up-on-unanswered-quotes.md)
- [Jobber API and MCP server: every tool](https://cotlet.dev/integrations/jobber-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Jobber.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Jobber.

[Sign up free](https://cotlet.dev/app/signup?app=jobber)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.