Connect Salesforce
With the PostBuddy package for Salesforce, a flow in your org can send a card, for example when an opportunity is won. The status of each card comes back to a Mail Item record in Salesforce. Owners, Admins and Developers can connect Salesforce; you also need a Salesforce administrator.
Connect in PostBuddy
- Open Integrations and choose Connect on the Salesforce card.
- Enter a Name and your Salesforce instance URL, for example https://yourcompany.my.salesforce.com.
- Choose the Status writeback: how status updates reach Salesforce.
- Choose Install.
- Copy the values that appear: the API key and, with a writeback, the webhook secret. They are shown only once.
| Status writeback | How it works |
|---|---|
| Connected App (recommended) | PostBuddy sends every status change to your org. You enter the Apex REST endpoint and the client id and secret of a Connected App. |
| Site guest user | PostBuddy sends status changes to a public Salesforce site. Only the signature protects it, so prefer the Connected App. |
| Polling from Salesforce (NONE) | Salesforce fetches the updates itself with a scheduled job. |
Tick Mirror every item, not only those created from Salesforce if Salesforce should also show cards sent from Postbatches or the API.
Finish the setup in Salesforce
Your Salesforce administrator then:
- Installs the PostBuddy package in your org and assigns the permission sets.
- Adds the API key as the ApiKey parameter of the PostBuddy API principal (Setup, Named Credentials).
- Pastes the webhook secret on the PostBuddy Setup tab and runs the connection tests.
- Creates a flow with the action "Send Mail Item" and the Postflow id from the portal.
Back in PostBuddy, choose Manage on the Salesforce card, open the installation and choose Run health check. The status changes to Connected when everything works.
Try your flow in a sandbox first, with the test mode input of the action set to true. Test items are never printed or charged. See Send a test item.
Manage the connection
Under Manage you see each connected org with its status and last activity.
- Configure changes the writeback settings.
- Disable stops the connection: items sent with its key are refused until you Enable it again.
- Remove integration revokes its API key and webhook endpoint. This cannot be undone.
- Connect another org adds a second org, for example a sandbox.
If the Salesforce card says Not in your plan or that it is no longer available for new connections, your existing connections keep working; only new ones cannot be added.
PostBuddy can disable a connection, revoke an API key or switch off a webhook endpoint when something goes wrong, for example repeated failures or a key that was made public. The Owners of your organisation then get a notification with the reason.
The setup guide for your Salesforce administrator has every step in detail: Salesforce integration guide.
Open a support ticket in the portal. Tell us what you tried and, if you can, which item or Postbatch it is about.