This is a paid bot, and its usage will be counted toward your plan's credits limit. For more information about credit usage, refer to this article.
How the Invoke Salesforce process on document completion bot works
Automatically update Salesforce record fields when altaFlow documents are completed. The bot maps completed document data to Account, Opportunity, Contact, Lead, or any custom Salesforce object — including related child or parent objects — without additional manual entry after signing. Be sure to set up the Salesforce process you need to initiate in advance.
Use case example: When prospecting new clients, you send them offers via altaFlow. Once a client accepts and signs, a checkmark automatically appears in the Salesforce record specifying that the individual offer has been accepted — no rep needs to update the CRM manually.
How to set up
When the bot works by default:
The bot activates after documents in a workflow have been completed. To add the bot to your workflow, click the plus icon.
Then, select Bot from the list.
Search for the Invoke Salesforce process on document completion bot. Then, install the bot to your workflow by clicking the corresponding button.
Connection settings
To connect the bot to your Salesforce organization, select Connect in the Connection settings section.
Then, select a Salesforce account to connect. You can also select a new account to connect (via the Production environment, Sandbox environment, or custom URL).
Once connected, select Continue to proceed.
In the Select objects and fields to update, select the base object (Account in the current example). A base object is an object where the fields will be updated with the data from the completed documents.
You can also select any related objects if needed. A related object is a child or parent object of a base object where the fields will be updated with the data from the documents.
Next, select the Salesforce fields you want the bot to update. You can enter a custom value manually if the information is static, or use a data variable if you want to use the data from the completed documents.
Then, select the Salesforce field you need to update with the specified value.
Once set up, select Continue to proceed.
Conditions
Set conditions to invoke Salesforce updates only in specific scenarios. Common use cases include:
Environment routing: Update Sandbox record when a "Test mode" field is on; update Production Salesforce records otherwise — safe for QA teams.
Signed-only updates: Trigger the Salesforce update only when a "Status" field equals "Signed" — prevents drafts from polluting your CRM.
Deal size gating: Update Opportunity records only when the deal value exceeds a threshold (e.g., $10,000) to avoid clutter from small transactions.
Skip on decline: Add a "decline reason is empty" condition to prevent Salesforce updates on voided or rejected documents.
Learn more about bot conditions usage in the dedicated bot execution conditions article.
Advanced settings
Fine-tune how the bot updates Salesforce records:
Run frequency: The bot fires once per workflow completion by default. Enable per-revision if the Salesforce record needs updates on every iteration (rare — creates API overhead).
Failure handling: If Salesforce API is unreachable or the record was deleted, choose whether to skip silently or halt the workflow for reconciliation. Stop is safest for compliance-critical records.
Document tags: Tag documents that triggered a Salesforce update (e.g., "salesforce-updated") for audit trails and API rate limit tracking.
Learn more about adjusting Advanced settings in the bot setup glossary.