This is a paid bot, and its usage will be counted toward your plan's credit limit. For more information about credit usage, refer to this article.
General
Automatically store completed documents in Salesforce for better document management and easy access by sales and legal teams.
Use case: At the start of a partnership, ensure sensitive information is protected by having both parties sign an NDA, then attach it to the CRM record.
How to set up
To add the bot:
1. Add a new action by clicking a plus icon.
2. Choose Bot and search for the Export documents to Salesforce bot.
3. Click on the bot to install it.
Trigger
A trigger is an event that causes the bot to start working. The bot can be placed only after a step or any other element (for example, another bot), and it will run once the previous element finishes its job.
Connection settings
In Destination, select an option to connect the bot to your Salesforce account. Choose the Salesforce account you want to connect.
Note: By default, exported documents are owned by the connected user account and are only available to that user in Salesforce. Administrators can change settings to alter ownership and access.
To add a new connection, choose a Salesforce instance (Production, Sandbox, or custom domain).
Select the base object where the documents will be attached. You can attach documents as files (editable, collaborative, searchable) or attachments (non-editable, with limited features).
Tip: To find attached documents, check the Notes & Attachments section on the Salesforce record page or look in the Files object.
Selecting documents
In Documents, select the documents to attach to the Salesforce record. If the documents already exist in a Salesforce record, you can choose to create a new one or replace the old one with the latest one.
Enable this option to keep fillable PDF fields editable in Salesforce.
Lookup
In Find record, set rules to locate the Salesforce destination record:
Sent by the airSlate Workflow integration app: The system auto-defines the record ID.
Tip: This option can be used only if you start the process from the Salesforce record that you want to pre-fill from. For example, Account is the base record, and the workflow starts from Account as well.
By bot lookup: Match document fields to record fields or custom values, like matching Account name.
Tip: This option can be used for workflows started outside or from Salesforce with different starting records. For example, if Account is the base record but the workflow starts from the Contact record.
Testing
In the Test section, check how the bot works by selecting Test. You will see a success message if everything is set up correctly. If there are issues, review the connection, mapping, or trigger configuration
.
If you skip testing by selecting Skip testing, you may miss issues with the bot setup. Testing is recommended to ensure everything works as expected.
Enter the ID of the record to which the document should be exported, but only if the starting record matches the base record.
Tip: To find the Salesforce record ID, go to the specific record and copy the ID from the URL.
Enter the matching value (like Account name) if you have set up a lookup for your workflow.
Conditions
Set conditions to control when the bot activates, tailoring it to your specific needs for more efficient automation. For detailed guidance, refer to this article.
Without defined conditions, the bot will default to activating whenever recipients complete the documents or the previous element (for example, another bot) finishes its job.
Best practice: If you configured the lookup to locate the Salesforce starting record, set conditions to ensure the lookup field is not empty.
Advanced settings
This section allows you to choose how the process proceeds in case the bot fails:
Select Proceed to allow the workflow to move to the next signer and automation if the bot isn't crucial.
Select Stop if the bot is critical; this prevents the next signer from receiving documents if data wasn't pre-filled from the source of your choice.