Integration recipe · HubSpot
Send a postcard when a new lead enters HubSpot
Enroll only qualified contacts with complete addresses. Send the contact ID to your Sendvo connection, then write the result back to HubSpot.
- Reviewed against primary sources
- Last updated: October 11, 2026
- No setup fees
The recipe
How do you send a postcard when a new lead enters HubSpot?
Use a contact-based workflow with a narrow enrollment rule.
- Create propertiesAdd mail eligibility, mail status, mailpiece ID, and exception reason properties.
- Build enrollmentRequire the intended lead source or lifecycle stage and a complete postal address.
- Send the eventUse the connection method that your HubSpot and Sendvo accounts support.
- Write backSave accepted, held, failed, and released results.
Read the full answer
The rule should identify the lead stage or source that is eligible for mail. Require structured postal fields. Pass the contact ID as the source key and a reviewed template ID as a controlled value. Test with a named contact that cannot enter a live release path. The same controls apply whether the event comes from a CRM workflow or a custom endpoint; direct mail API guidance sets out the record fields and retry rules.
Do not use 'contact created' if imported, test, partner, or suppressed contacts can also meet that event.
How it connects
The HubSpot record explains every send.
Field map
Keep trigger and result properties apart.
Separate source and mail-result properties so an update cannot retrigger itself.
| HubSpot property | Mail field | Rule |
|---|---|---|
| Record ID | source_record_id | Required. Not email alone. |
| First name | first_name | Fallback or hold if the card needs it. |
| Street address | address_line_1 | Required for release. |
| City, state, ZIP Code | city, state, postal_code | Separate fields. |
| Mail eligibility | send_rule | Set before enrollment. |
| Mail status | result | Never in the same enrollment trigger. |
| Mailpiece ID | mailpiece_id | Save the returned join key. |
HubSpot FAQ
Check these before enrollment.
Pricing it out? See plans and per-piece rates.
Primary sources
No native HubSpot 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 send a postcard after a HubSpot form submission?
Enroll on the exact form and then check mailing eligibility. Form submission identifies an event. It does not guarantee a complete or correct mailing address. Keep each address field separate, validate required values, and reuse the submission or contact event key on retries.
If a contact can submit the form more than once, define eligibility for each submission and apply duplicate and suppression rules.
How do you write mail status back to HubSpot?
Update dedicated contact properties with the workflow result and join keys. Store the latest operational state, exception reason, source event ID, campaign ID, and mailpiece ID. Use a timestamped history outside one overwrite-only property when you need a full audit trail.
Do not label a mailstream event as a response or revenue event. Use separate properties for actual responses.
Does HubSpot include workflow webhooks on every plan?
No. Availability depends on the HubSpot product and subscription. Check the official workflow documentation and your account.
Is this a native Sendvo HubSpot integration?
No native connector is claimed. The path can use Zapier, a webhook, or an approved API connection.
Can the mail-status property retrigger the workflow?
Yes, if enrollment rules include that property. Keep trigger and result properties separate and test re-enrollment behavior.
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.
Let the HubSpot record explain every send.
Use a narrow enrollment rule, a stable contact ID, complete postal fields, and clear result properties.