Sending a Test Email to Your Mailhook Address

Generate a Mailhook address, email it from your own inbox, and watch the run start within seconds, then confirm your From allowlist and Subject regex filters behave the way you expect.

Overview

A Mailhook trigger gives your workflow a unique inbound email address. Any message sent to that address starts a run, usually within seconds, with no mailbox or OAuth connection involved. Before you point a vendor, a forwarding rule, or a system mailer at it, the safest move is to send a test email yourself and confirm the workflow actually fires. This guide walks through that test-send-and-verify loop end to end, including how the optional From allowlist and Subject regex filters decide whether a given message gets through.

Think of the test email as a dry run of your real source. When you send from your own inbox, you control the From address, the subject, and the body, so you can deliberately match or break a filter and see the difference in execution history. In Spojit, every inbound message that passes the filters produces a normal execution you can open and inspect, exposing the parsed email under {{ input }}. Once your test message starts a run and the data looks right, you can confidently hand the address to whatever system will send to it in production.

Before You Start

A workflow open in the Workflow Designer with a Trigger node already on the canvas.
Access to an email account you can send from (your normal work or personal inbox is fine).
If you plan to test filters, decide in advance which From address and subject should pass and which should be rejected.

Steps

Step 1: Generate a Mailhook address

Select the Trigger node on the canvas to open its properties panel. Set Trigger Type to Mailhook. Optionally set an Address prefix (1 to 24 characters, default mh) so the address is easy to recognise in your inbox. Click Generate email address. Spojit creates a unique address in the form <prefix>-<random16>@mailhook.spojit.com. Use the copy control next to the address to put it on your clipboard, then save the workflow so the trigger is active.

Step 2: Send a test email from your own inbox

Open your normal email client and compose a new message. Paste the Mailhook address into the To field. Give it a recognisable subject such as Spojit mailhook test and a short body. Send it. A Mailhook fires whether the address appears in To, Cc, or Bcc, so any of those fields work for the test. The trigger is push based, so delivery typically reaches Spojit within seconds rather than waiting on a poll interval.

Step 3: Watch the run start

Open the workflow's execution history (the Executions view for the workflow). A new run should appear shortly after you hit send. Open it and inspect the trigger output, which is available to downstream nodes as {{ input }}. You should see your test reflected in fields such as {{ input.from }}, {{ input.subject }}, {{ input.text }}, and {{ input.receivedAt }}. Recipients land in {{ input.to }}, {{ input.cc }}, and {{ input.replyTo }}, and any files you attached appear as references under {{ input.attachments }}. Confirming these values is the proof that your address is live and parsing mail correctly.

Step 4: Test the From allowlist filter

If you have set a From allowlist on the Mailhook trigger, only senders that match it start a run. To verify it, send one test from an address that is on the list and confirm a run appears, then send a second test from an address that is not on the list and confirm that no run appears. A message that is rejected by the allowlist simply does not produce an execution, so the absence of a new run is the expected (and correct) result. This is the cleanest way to prove the allowlist is doing its job before a real vendor starts emailing the address.

Step 5: Test the Subject regex filter

If you have set a Subject regex, only messages whose subject matches the pattern fire the workflow. Send one test with a subject that matches the pattern and confirm a run starts, then send another with a subject that deliberately does not match and confirm it is ignored. Because both the From allowlist and the Subject regex must pass, a single failed match in either filter means no execution. Adjust the subject of your test message until you see the pass and fail behaviour you intend, then you know production mail will be filtered the same way.

Step 6: Reply to yourself with a Send Email node (optional)

Mailhook runs are always asynchronous, so the sender receives no automatic reply. If you want a visible confirmation in your inbox, add a Send Email node after the trigger and set its Recipients to {{ input.replyTo }}. When your test fires, Spojit sends a message back to you from its built-in mail service. This is a handy way to confirm the full round trip without opening the Executions view, though external recipients must be on your org allowlist under Settings -> General -> Email recipients.

Tips

Keep your test subject distinctive (for example Spojit mailhook test) so the matching run is easy to spot in execution history.
Mail is deduplicated per message, so resending the exact same message may not start a second run. Change the subject or body slightly between test sends.
You can ask Miraxa, the intelligent layer across your automation, to explain what each {{ input }} field contains while you are looking at the trigger output on the page.
Received emails are retained for 30 days, so a test you send today remains inspectable for a month if you need to revisit the parsed data.

Common Pitfalls

No run appears and you have filters set. An empty execution history after a test is usually the From allowlist or Subject regex rejecting the message, not a fault. Send a test that you know matches both filters to confirm the address itself is working.
Testing after a Regenerate address. Using Regenerate address rotates the address and the old one dies instantly. If you copied the address earlier, re-copy the new one before sending, or your test will bounce.
Expecting a reply to the sender. Mailhook never replies to the sender automatically. If you need a confirmation email, add a Send Email node addressed to {{ input.replyTo }}.
Forgetting to save. The trigger is not live until the workflow is saved. Send your test only after saving, or the message will have nowhere to land.