Skip to main content

Documentation Index

Fetch the complete documentation index at: https://documentation.outpost.pub/llms.txt

Use this file to discover all available pages before exploring further.

Bespoke — Salesforce integrations are configured by the Outpost team for each publication. Every Salesforce instance is different (object shape, custom fields, validation rules, automation), so there is no one-size-fits-all setup. Contact support@outpost.pub to start a Salesforce integration.
Outpost can sync member data into your Salesforce instance. The most common shape is Account objects — useful for B2B publications where members represent organizational accounts — but every implementation is tailored to the Salesforce setup the publisher already has.

​
What we typically sync

The Outpost team designs the sync to your Salesforce schema. A baseline implementation pushes the following member data outward:
Outpost dataTypical Salesforce fieldNotes
First nameFirstNameFalls back to “FirstNameAnonymous” if blank.
Last nameLastNameFalls back to “LastNameAnonymous” if blank.
EmailPersonEmailThe member’s email address.
Member IDGhostID__cCustom field used to match Outpost members to Salesforce records.
Membership typeType”Free subscriber”, “Monthly Subscriber”, or “Annual Subscriber”.
Newsletter opt-outNewsletterOptOut__cWhether the member has opted out of newsletters.
Marketing opt-outPersonHasOptedOutOfMarketingEmail__cWhether the member has opted out of marketing emails.
Donor statusDonor__cWhether the member has tipped or donated.
Custom fields, object types (Account, Contact, Lead, custom), and field names are confirmed and adjusted during the bespoke setup conversation.

​
Membership-type mapping

The default mapping from Outpost’s subscription state to Salesforce membership type:
Member statusSalesforce type
Free member”Free subscriber”
Monthly paid subscriber”Monthly Subscriber”
Annual paid subscriber”Annual Subscriber”
Complimentary subscriber”Annual Subscriber”
This mapping can be overridden during setup if your team uses different terminology in Salesforce.

​
Data flow

Sync is one-way — Outpost pushes member events to Salesforce. Changes made directly in Salesforce are not pulled back into Outpost.
Outpost eventWhat we send to Salesforce
New member signs upCreate or upsert the Salesforce record matched on GhostID__c.
Member status changes (upgrade, downgrade, cancel, renew)Update the membership-type and status fields.
Member opts out of newsletters or marketingUpdate the corresponding opt-out fields.
Member tips or donatesUpdate the donor field.
Updates run as background jobs in near real-time. Failed jobs retry automatically up to three times with increasing delays. Removing a member in Outpost does not delete the Salesforce record — your CRM keeps the historical data.

​
Setup process

There is no in-app self-serve connect button. Setting up Salesforce takes a brief discovery call with the Outpost team:
1

Reach out

Email support@outpost.pub with a short description of how your Salesforce instance is set up — the object types you use for members, any required custom fields, validation rules we should know about.
2

Discovery

The Outpost team reviews your Salesforce schema and confirms the field mapping with you.
3

Credentials

We coordinate Salesforce credentials securely. Production setups typically use a Salesforce-side OAuth-connected app or a service user with a security token; we’ll guide you through the option that fits your security policy.
4

Initial sync + go-live

Outpost runs an initial sync to backfill existing members, verifies the data lands correctly, then enables live sync for new events.

​
Common custom fields

If you’re getting your Salesforce instance ready before reaching out, the integration is easier when the following custom fields exist on the object that will hold member records (commonly Account):
  • GhostID__c — Text, length 255, marked Unique. Required — used to match Outpost members to Salesforce records.
  • NewsletterOptOut__c — Checkbox.
  • PersonHasOptedOutOfMarketingEmail__c — Checkbox.
  • Donor__c — Checkbox.
These are starting points — your schema may already cover the equivalent state under different names, in which case we map to those during setup.

HubSpot Integration

Less custom alternative for publications without an existing CRM.

Members

The member records that get synced to Salesforce.

Labels

Outpost applies labels to track Salesforce-synced members.

​
FAQ

Every Salesforce instance differs in object shape, validation rules, automations, and required fields. A one-size-fits-all integration would either break instances with custom validation or skip useful data. Bespoke setup means we map to the way your team actually uses Salesforce.
No. Outpost pushes data to Salesforce. Changes made directly in Salesforce are not pulled back to Outpost.
No. The Salesforce record remains so your CRM keeps the historical data.
Any edition with API access. That covers most Professional, Enterprise, and Unlimited editions. Check that API access is enabled in your Salesforce admin settings before reaching out.
Yes. The default shape is Account-based, but the Outpost team can configure the integration to use Contact, Lead, or a custom object during setup.