What do we check?
For every plugin you have installed, we run a harmless read-only call against the service's API (a 'who am I?'-style endpoint). It validates that the API key still works, without fetching customer data or changing anything.
- Gecko Booking: GET /api/v1/customer?rowsPerPage=1
- Billy: GET /v2/organization
- Cal.com: GET /v2/me
- Calendly: GET /users/me
- Pipedrive: GET /v1/users/me
- Shipmondo: GET /api/public/v3/account
When does the check run?
Mondays at 06:00 UTC (≈ 08:00 Central European Time). Every Monday, all installed plugins. You can also run the check manually at any time by clicking 'Test connection' on the plugin detail page.
The result shows as an 'Active' / 'Failed' / 'Not tested' pill on the plugin page, along with 'Last tested X ago'.
What happens if it fails?
- The plugin status flips to 'Failed' and the error message is stored (typically 'Invalid API key' or an HTTP status code).
- We send you one email about the problem — no more until either it works again, or a NEW type of error shows up.
- The AI can still write drafts, but can no longer call the failing plugin while drafting. Your other plugins keep running independently.
- You fix it by entering a new API key on the plugin detail page — we test the new key right away before saving.
Why not more often?
We want to stay up to date without spamming third-party APIs, and without emailing you every day because a key has been broken since Tuesday. A weekly cadence strikes that balance — and you always have the 'Test connection' button if you're suspicious.