CRM
Salesforce
Send mail from Salesforce — via Flow HTTP callouts or Apex, whichever fits your team.
What it does
How Salesforce works with Intelliprint.
Salesforce runs your pipeline. Physical mail should live in the same place as every other outreach channel, not in a separate tool that marketing logs into. Mail sent from Salesforce means account-based campaigns, lost-deal re-engagement letters, VIP thank-yous, and regulated-industry compliance mail — all recorded against the contact or account where they belong.
Two routes work today, each fitting different teams. For admins comfortable with Flow: an HTTP Callout action calls the Intelliprint API directly from a record-triggered Flow — no code, full access to letters, postcards, and direct mail. Because Salesforce doesn't allow external callouts on a Flow's default immediate path, the callout runs on an Asynchronous Path, which executes right after the record save completes. For developer-led orgs: Queueable Apex (Salesforce's current recommendation over legacy @future methods) calls into the API with full control over batching, retry logic, and error handling.
Regardless of route, Salesforce data flows to Intelliprint through the authenticated API. Webhook callbacks from Intelliprint can update custom fields or log activity records, so sales reps see production events ('Letter sent'), delivery confirmation, and returned mail inside Salesforce.
Common use cases
What teams build with Salesforce + Intelliprint.
- Account-based direct mail campaigns triggered from Opportunity stage changes (Flow or Apex)
- Lost-deal re-engagement letters after Closed Lost > 90 days (Flow or Apex)
- Physical thank-you letters on first Opportunity close (Flow or Apex)
- Compliance mail from financial services orgs (Flow or Apex)
- High-value gift-with-letter for new customers above an ARR threshold (Flow or Apex)
Set-up
Get connected in 5 steps.
Choose your route
Salesforce Admin sending postcards or direct mail, no code? Use Flow with an HTTP Callout action on an Asynchronous Path. Developer team who wants full control over retries and batching? Use Queueable Apex.
Set up authentication
Create an External Credential for your Intelliprint API key, then a Named Credential that points at the Intelliprint API and links to it. Grant access via a Permission Set — without one, the callout fails even when the credential is configured correctly.
Upload your template
Design and upload your mail template in Intelliprint. Include merge variables for contact, account, and opportunity fields you'll pass from Salesforce.
Build the trigger
Flow: record-triggered Flow → Asynchronous Path → HTTP Callout action → map fields to the API payload. Apex: a trigger can't call out directly, so delegate to a Queueable class (or a simple @future(callout=true) method) that calls the API via HttpRequest/Http, using the Named Credential as the callout endpoint.
Test in sandbox, then deploy
Test with one record in a sandbox. Confirm the API call succeeds, the mail preview is correct, and callbacks log to the right place in Salesforce. Then deploy to production.
Ready to send mail from Salesforce?
Free to start. No setup fees, no minimum order.