01 · Direct answer
How do you send a postcard when a HighLevel pipeline stage changes?
Filter on the target pipeline and stage. Require a complete postal address. Send the contact ID, opportunity ID, trigger time, template ID, and address fields. Use the opportunity-stage event as the duplicate key.
Do not use only the contact ID when one contact can move through multiple opportunities.
- Select the eventUse the exact pipeline and stage that makes mail useful.
- Map the recordInclude contact and opportunity IDs plus structured postal fields.
- TestUse a test contact and the approved non-mailing Sendvo path.
- Write backStore accepted, held, failed, or released in a custom field or activity record.
02 · Direct answer
How do you write direct-mail status back to HighLevel?
Store the mailpiece ID, current operational state, exception reason, and last event time. Keep response and revenue fields separate from mailstream status.
If the writeback updates an opportunity, confirm that it does not replay the pipeline-stage workflow.
Implementation worksheet
HighLevel workflow map
Use IDs for joins and human-readable fields for review. Do not depend on names as keys.
| HighLevel field | Mail field | Rule |
|---|---|---|
| Contact ID | recipient_key | Required. |
| Opportunity ID | source_record_id | Required when the trigger is a pipeline event. |
| Pipeline and stage | trigger_reason | Record the exact eligible value. |
| Address fields | postal address | Hold incomplete records. |
| Custom template value | template_id | Use an approved fixed value. |
| Mail status custom field | result | Exclude it from the send trigger. |
Preflight checklist
- 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.
FAQ
Questions to resolve before launch
Does HighLevel support outbound workflow webhooks?
HighLevel documents a Webhook workflow action. Check current plan and action access in your account.
Is this a native Sendvo HighLevel integration?
No native connector is claimed. The recipe uses an approved webhook or other confirmed connection.
What prevents duplicate postcards?
Use a stable opportunity-stage event key and a defined send window. Reuse the key on retries.
Primary sources
Sources and review notes
- HighLevel: Workflow Webhook actionOfficial outbound webhook action and configuration.
- HighLevel: Pipeline Stage Changed triggerOfficial pipeline-stage trigger guidance.
Product plans, trigger names, and connector access can change. Check the linked documentation and your account before production use. Sendvo last reviewed these sources on August 31, 2026.