The integration does two jobs. It gives a Zap a test address and then hands back the report for the email that arrived there. It also keeps a permanent address that you subscribe to your own newsletter or welcome sequence, and every issue sent to it comes back to the Zap with its score and its problems.
Connecting
The integration is waiting for Zapier's review, so it is not in Zapier's app directory yet. Until it is, this invite link adds it to your Zapier account. Then get a key with the form above and paste it when Zapier asks you to connect Email Spam Tester. The key is free. It belongs to the email address you typed, and the address is also the connection's name in Zapier. Nothing is mailed to you and there is no password: if the key gets lost, ask for a new one with the same address. Old keys keep working.
What it can do
- Create Test Address, an action. A single-use address for one email, valid for an hour. Send to it from whatever app normally sends your email, Gmail or your ESP, so the report covers that app's real servers and signature. Switch on the folder check and the action also returns about 30 test mailboxes at a dozen providers and a marker for the subject; send the same email to all of them and the report shows Inbox, Promotions or Spam for each provider. The Gmail ones are public test mailboxes, where anyone can see the subject, the sender name and the folder, so keep confidential email out of the folder check.
- New Report, a trigger. Fires when an email sent to one of your test addresses has been checked. You get the score out of 100 and the classic 0 to 10, the subject, the sender, one line per problem and per warning, the titles of the fixes and the link to the full report.
- Find Report, a search. The same fields for one test, looked up by its ID. While nothing has arrived, Status says
waiting, which a filter step can wait on. - Create Permanent Mailbox, an action. An address that does not expire, for one sending domain. Subscribe it to your newsletter or your welcome sequence.
- New Email in Permanent Mailbox, a trigger. Fires for each email that arrived at that address and has been checked, with the same fields. These reports are private: there is no public link, and only your key reads them.
A few Zaps to start with
- Every Monday, Schedule by Zapier creates a test address, Gmail sends your template to it, and twenty minutes later Find Report fetches the score for a Slack message.
- New Email in Permanent Mailbox, then a filter on Score below 70, then an email to whoever owns the newsletter, with the problems in the body.
- Each new report goes as a row into Google Sheets, so a sending domain's score is tracked week after week.
Limits
Each key gets 50 tests a day, 3 of them with the folder check, and up to 5 permanent mailboxes that each take 300 emails a day. Past the test limit, Create Test Address stops with the reason and the time it opens again, and past the folder check limit it stops until the next day. A mailbox that gets more than 300 emails in a day keeps the rest without checking them that day. Tests on the website are not affected.
Data
Test reports work as they do on the site: anyone with a report's link can open it. Emails to a permanent mailbox are kept apart, and their reports open only with your key. Such an email is deleted two days after it arrives, and its report after 90 days. The privacy policy has the details, and the API reference lists every call the integration makes.