Integration recipe · Follow Up Boss
Send postcards on Follow Up Boss stage changes
Trigger on one named stage. Send the person ID, mailing address, and template, and keep the mail result outside the trigger.
- Reviewed against primary sources
- Last updated: October 11, 2026
- No setup fees
The recipe
How do you send a postcard when a Follow Up Boss lead changes stage?
Trigger on one named stage and resolve one intended mailing address.
- Name the stageUse the stage that proves the follow-up moment.
- Choose the addressSelect contact mailing address or property address with a written rule.
- TestMove a test person through the stage with live release disabled.
- Record the resultSave mailpiece ID and exception reason without replaying the trigger.
Read the full answer
Use the Follow Up Boss person ID as the recipient key. Record the prior and new stage when the connector exposes both. Map the selected mailing address and a reviewed template. Use a stage-event key to stop retries or repeat updates from creating another piece. If your team would rather connect an endpoint directly, start with the direct mail API guidance.
Real-estate records often contain both a contact address and a property address. State which one receives the postcard.
How it connects
Person, property, and mailbox stay separate.
Field map
Decide which address is the mailbox.
Property location and recipient mailing address are not interchangeable.
| Follow Up Boss value | Mail field | Rule |
|---|---|---|
| Person ID | recipient_key | Required and stable. |
| Stage | trigger_reason | The exact eligible value. |
| Contact mailing address | Postal address | When the card goes to the person. |
| Property city | personalization.property_city | Copy only, unless it is the recipient address. |
| Template key | template_id | Pin a tested version. |
| Note or custom field | result | Outside stage-trigger logic. |
Follow Up Boss FAQ
Check these before the first stage.
Pricing it out? See plans and per-piece rates.
Primary sources
No native Follow Up Boss connector claimed. Plans: list upload, dedupe, and automated mail need Operator or Growth. Integrations and API access need Growth and connect through a no-code tool or our API. Product plans, trigger names, and connector access can change. Confirm yours before production use.
How do you write mail status back to Follow Up Boss?
Use a note, custom field, or connected activity that preserves the source event ID. Write accepted, held, failed, or released with the mailpiece ID and event time. Keep operational status separate from response or conversion claims.
If the writeback edits the person, confirm that the stage automation does not re-run.
Is Follow Up Boss stage change available in every connector?
Do not assume it is. Confirm the exact trigger, polling behavior, and available fields in the connection you will use.
Which address should receive the postcard?
Choose the contact mailing address unless the documented workflow intentionally mails another party. Property address can be personalization data without being the destination.
Is this a native Sendvo connector?
No native Follow Up Boss connector is claimed.
Before launch
Preflight checklist before the first live send
- Use one stable source-event ID and save it with the mail record.
- Require recipient name, address line 1, city, state, and ZIP Code before release.
- Set a duplicate rule for the person, household, property, order, or job.
- Render a proof with a test record before any funded send.
- Define who can pause the workflow and who can approve release.
- Store the source record ID, campaign ID, and returned mailpiece ID together.
- Treat mailstream events as operational signals, not proof of attention or revenue.
Keep person, property, and mailbox distinct.
Confirm the stage trigger, choose one address rule, test duplicate behavior, and save the result with the person ID.