How do you send a postcard when a new lead enters HubSpot?

Use a contact-based workflow with a narrow enrollment rule.

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.

Do not use 'contact created' if imported, test, partner, or suppressed contacts can also meet that event.

  1. Create propertiesAdd mail eligibility, mail status, mailpiece ID, and exception reason properties.
  2. Build enrollmentRequire the intended lead source or lifecycle stage and a complete postal address.
  3. Send the eventUse the connection method that your HubSpot and Sendvo accounts support.
  4. Write backSave accepted, held, failed, and released results.

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 whether each submission is eligible or whether a send window suppresses repeats.

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.

HubSpot property map

Keep source properties and mail-result properties separate so an update cannot retrigger itself.

HubSpot propertyMail fieldRule
Record IDsource_record_idRequired. Do not use email as the only key.
First namefirst_nameFallback or hold if the creative requires it.
Street addressaddress_line_1Required for release.
City, state, ZIP Codecity, state, postal_codeUse separate fields.
Mail eligibilitysend_ruleSet before enrollment.
Mail statusresultDo not use it in the same enrollment trigger.
Mailpiece IDmailpiece_idSave the returned join key.

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.

Questions to resolve before launch

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.

Sources and review notes

  1. HubSpot: Use webhooks with workflowsOfficial webhook action and subscription notes.
  2. HubSpot: Create workflowsOfficial enrollment and workflow configuration.
  3. HubSpot CRM contacts APIOfficial contact record and property API 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.