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
Use the Export record to MS Dynamics 365 bot to create or update records in MS Dynamics 365.
Use case example: When collecting Purchase orders from your customers, you need to automatically create records for new customers or update the existing customer information in MS Dynamics 365 records.
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 record to MS Dynamics 365 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, connect the bot to your Microsoft account by clicking the Connect button.
In the pop-up, enter your MS Dynamics 365 instance URL. Copy it from the address bar when you’re in your organization and click Select after pasting it. In the screenshot, you can see an example of how it must look like.
You’ll be redirected to the Microsoft login screen. Once you’ve logged in, you’ll be directed back to WorkFlow.
Using the three-dot connection menu, you can disconnect the current account or connect to different accounts anytime.
Select a base object in MS Dynamics 365 where to export files (1). Click Continue to proceed (2).
Lookup
In the Find record section, select the action that should be performed to the record in MS Dynamics 365:
Action | Explanation |
Always add a new record | A new record will be created every time the bot runs. Use this option if you want to ensure that a new record is always added, without any updates to existing ones.
|
Update an existing record | An existing record in CRM will be updated if a matching row is found. Use this option if you want to modify existing records and avoid creating new ones. |
Update a record or create one if none is found | The bot will try to find an existing record in CRM and update it if a match is found. If no match is found, it will add a new record. Use this if you want flexibility — to update existing records or add new ones when needed. |
Tip: If you choose Only update if a match is found or Update or add if no match is found, specify how the bot will find the correct MS Dynamics 365 record by matching object fields to document field values, signer details, or custom values.
Start by selecting an object field that must work as an identifier.
Then, select the value type that your object field must match.
Value based on | Explanation |
Document field value | This option allows the bot to find records by matching the value in the specified object field with a corresponding value in a document field.
For example, if your document has a field that captures a record ID or name, the bot will search for records where the object field contains this value.
|
Signer details | This matching type uses the details the signer provides, such as their email, first name, or last name, to find a corresponding record in the object.
It’s useful for workflows where the signer’s identity must be cross-referenced with your system's records. |
Text input | This option allows you to manually enter a custom text value, which the bot will use to find a matching record in the object.
This is particularly useful when the value to be matched isn't defined by the document or the signer but is a specific input the workflow creator provides.
|
Click Continue to proceed to the next section.
Mapping
In Data mapping, select Map fields. Drag and drop MS Dynamics 365 fields onto document fields. Blue highlights show available fields. Mapped field names appear on the canvas.
Testing
In the Test section, simulate the bot's performance by clicking Test.
For testing, you’ll have to provide valid data for all mapped fields. A success message confirms proper configuration. Any errors will be displayed as an error message.
Note: Testing the bot will update or create a real record in MS Dynamics 365. To prevent changes to actual data, use test records instead of real ones during setup and testing.
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.
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.