Changing Your Mailhook Email Address

Regenerate a workflow's mailhook address, or change the prefix it uses.

Overview

Each mailhook trigger has one address made of two parts: a prefix you can choose (for example invoices) and a random token Spojit generates (for example x7k2m9qf4a3vbn8c), joined as invoices-x7k2m9qf4a3vbn8c@mailhook.spojit.com. The random token is what keeps the address unguessable, so changing the address means generating a new token. There is no way to hand-pick the full address.

You would regenerate an address when it has spread further than you intended (pasted into a support ticket, shared with an offboarded vendor, visible in a screenshot), or simply when you want a different prefix on it.

Regenerating the Address

1. Open the workflow and click the Trigger node.
2. If you want a different prefix, update the address prefix field first. Leave it as is to keep the current prefix.
3. Click Regenerate address.
4. Click it again to confirm. The button warns you because the old address stops working at that moment.
5. Copy the new address and update every place that sends mail to it.

What Happens to the Old Address

• The old address stops routing immediately. There is no grace period or overlap window.
• Mail sent to the old address is discarded silently. It does not bounce, and the sender gets no error.
• Runs already started by the old address are unaffected; they continue normally.

Changing Only the Prefix

The prefix is cosmetic; the random token is what makes the address yours. Editing the prefix field does not change the current address. The new prefix is applied the next time you click Regenerate address. This means a prefix change always comes with a fresh token, which is intentional: any address change invalidates the old one, so it is treated as a rotation.

Prefix rules: 1 to 24 characters, lowercase letters, digits, and hyphens (no leading or trailing hyphen). If the field is empty, the default mh is used.

Tips

• Before regenerating, list everywhere the old address is used: vendor portals, forwarding rules, scripts. Update them all immediately after rotating.
• If you cannot update all senders at once, consider creating a second workflow with its own mailhook for the new senders and migrating gradually.
• Pausing a trigger with the Active toggle keeps the address. Use pause for temporary stops and regenerate only when you want the old address gone for good.

Common Pitfalls

• Silent mail loss after rotating - Because old-address mail is discarded without a bounce, a forgotten forwarding rule fails invisibly. Send a test email from each source after rotating.
• Expecting the prefix edit alone to rename the address - It does not. The address only changes when you regenerate.

Related Articles

• Setting Up a Mailhook Trigger
• Filtering Mailhook Emails
• Setting Up an Email Trigger
• Setting Up a Webhook Trigger

Learn More

• Mailhook trigger documentation