Deliverability monitoring belongs in the same workflow as sending, not in a sidebar dashboard nobody checks. Our OAuth 2.0 flow means Zapier, Make, n8n, and any other tool that speaks OAuth can call Inbox Check with real user-scoped authentication.
Actions & triggers
- Action: Run placement test. Input draft + providers, get test token.
- Action: Get test result. Poll test, return placement + per-provider breakdown.
- Trigger: Placement drop. Fire when weekly placement drops > X points.
- Trigger: Folder flip. Fire when a provider moves your mail to Spam post-send.
- Trigger: Auth record change. Fire when SPF/DKIM/DMARC unexpectedly changes.
Common automations
- Every new campaign draft gets auto-placement-tested before send (Zapier/Make).
- Weekly digest into client-specific Slack channels (n8n).
- Sequence auto-pauses when folder flip detected.
- Ticket auto-created in HelpScout/Linear when DMARC alignment breaks.
Setup
- In Zapier: “Inbox Check” app, sign in via OAuth prompt.
- In Make: “Inbox Check” module, add OAuth 2.0 connection.
- In n8n: community node
inbox-check, add OAuth2 credential. - Custom: hit
/oauth/authorize→/oauth/token, use bearer token on API calls.
Free integration use
No paid tier required for OAuth or integrations. Sign up and connect in 2 minutes.
FAQ
Does OAuth give me higher rate limits?
Yes — authenticated tokens get 5–20x the anonymous limits, depending on tier.
Can I use OAuth headers in my own code?
Yes — it's standard OAuth 2.0. Bearer token on the Authorization header works from any client.
What scopes exist?
read:tests, write:tests, read:monitor, write:monitor, plus a catch-all 'full' for trusted tokens. Minimum-scope defaults.
Related reading