Resend

Quick links

What the Resend integration does

Resend lets Superpractice send marketing emails through your verified sending domain. It can also sync new contacts to Resend and add them to segments, either all of them with auto-sync or selectively with list routing rules.

Setup

1. In Resend, verify the domain you want to send from.
2. Create a Resend API key.
3. In Superpractice, open Settings > Integrations > Resend.
4. Paste the API key and click Connect Resend.
5. Open Configure.
6. Set the default from name and from email.
7. Optionally turn on Auto-sync contacts and choose a segment in Auto-add to segment.
8. Click Save Settings.

Auto-sync contacts

Auto-sync adds every new contact with an email address to your Resend contacts as it is created, however the contact arrives: a website form, a call, a Meta or Google lead form, a booking, a landing page, a text, a webhook, or an import.

• Auto-add to segment is optional. Leave it at None (contacts only) to add contacts without a segment, or choose one segment that every synced contact joins. Resend sends a broadcast to a segment, so pick one if you want to email all your new contacts together.
• Contacts without an email address are skipped, since Resend needs one.
• Only contacts created after you connect Resend are synced. Contacts you already had are not added.
• A contact already in Resend is left as it is. Their name and unsubscribe status don't change.
• If Resend is busy or briefly unavailable, Superpractice retries automatically, so a new contact can take a few minutes to appear.

Use auto-sync when you want your full contact list mirrored in Resend.

List routing rules

List routing rules add contacts to specific segments based on how the contact was acquired and how it is tagged. Use rules when different segments should receive different emails. For example, contacts tagged guide-download go to a Guide Downloaders segment, while contacts tagged webinar go to a separate webinar segment.

1. In the Resend configuration dialog, find List routing rules.
2. Click Add rule, optionally give the rule a name so it's easy to recognize, and choose the target segment. Rules collapse to a one-line summary; click a rule to expand and edit it.
3. Optionally select attribution channels the contact must have come from.
4. Optionally select tags; the contact matches when it has any of the selected tags.
5. Optionally select Meta lead forms; the contact matches when it was created from any of the selected forms. This condition appears when Meta Ads is connected with lead form sync enabled.
6. Save settings.

How matching works:

• A condition left empty matches every contact. A rule with no conditions adds every contact to its segment.
• Within a condition, values match any: selecting two tags matches contacts with either tag.
• Across conditions, a contact must match both: a rule with a channel and a tag only adds contacts that match the channel and have the tag.
• Channels and Meta lead forms use the contact's first-touch attribution, the same way outbound webhook filters do. Only contacts created from a Meta lead form can match a lead form condition.

Rules run when a contact is created and run again whenever tags are added to a contact. This means tag-based rules still work when the tag arrives after the contact — for example tags applied automatically from Meta lead forms, or tags added later by your team.

A contact that is already in Resend is still added to the segments its rules match.

Rules only ever add contacts to segments. Removing a tag does not remove the contact from a segment; manage removals in Resend.

You can create up to 20 rules. Rules are independent of auto-sync. You can use either or both.

Sending identity

Use a from name recipients recognize. A personal sender name often performs better than a generic firm name. The from email must use a verified Resend domain.

Test sending

1. Create or open a test campaign in Superpractice Email.
2. Send a test email to an internal address.
3. Confirm the from name, from email, subject, links, and formatting.
4. If the email does not send, confirm the Resend domain is verified and the API key is still active.