---
title: "Sync Data with Salesforce"
canonical: "https://help.agiloft.com/space/HELP/619708428/Sync+Data+with+Salesforce"
format: markdown
---
This article guides you through activating each of the Agiloft Salesforce community recipes to automate the synchronization of data between Agiloft CLM and Salesforce. For instructions on downloading the recipes, see [Download Salesforce recipes](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/621281283/Set+Up+Salesforce+Integration#download_recipes).

> ℹ️ **Prerequisites**
> ℹ️ 
> ℹ️ - Before you start setting up recipes, make sure the Salesforce integration setup is complete. See [Set Up Salesforce Integration](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/621281283).
> ℹ️ - If you’re new to Integration Hub and Workato recipe concepts, see [Design Integration Hub Recipes](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/597655630) for an introduction and references to more information.

# Sync Salesforce data to Agiloft CLM

This section provides instructions for activating each of the recipes that sync data from Salesforce to Agiloft CLM.

> ℹ️ **Tips**
> ℹ️ 
> ℹ️ - The recipes are triggered when outbound messages are received. You configure the outbound messages and flows to send them from Salesforce.
> ℹ️ - Outbound messages must send all of the fields that the trigger retrieves. It’s easiest to configure messages to send all available fields.
> ℹ️ - When a recipe syncs data to your KB, it also updates the Salesforce record with the Agiloft record ID and applicable sync timestamps or errors. Those updates can trigger recipes again. To prevent recipe loops, it’s best to add conditions to Salesforce Flows so they don’t send outbound messages when records are updated by the recipe owner, typically the Agiloft CLM integration user. The recipe setup instructions below include steps for implementing flow conditions to prevent loops.

To get started, select what you want to do:

<details>
<summary>Accounts to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Upsert Account/Company** recipe to automate creating or updating Company records in your KB when Accounts are created or updated in Salesforce.

- The actions check for a matching Company and update the existing record or create a new one, then update the sync details in the Salesforce record.
- To trigger the recipe, configure a Salesforce flow to send an outbound message when an Account is created or updated. To prevent recipe loops, the flow includes two conditions: one to exclude updates made by the recipe and another to prevent triggering this recipe if the account was already synced.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Upsert Account/Company recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Account and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when an Account is created or updated:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Account as the Object.
  5. Trigger the flow when a record is created or updated.
  6. Now, set entry conditions to prevent recipe loops:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the first condition, select Last Modified By ID for Field and Does Not Equal for Operator.
    3. For Value, enter the Salesforce ID of the Agiloft CLM integration user. To get the ID, open the user’s Lightning record page, then copy the ID from the URL.
    4. Now, click Add Condition.
    5. For the second condition, select Agiloft Company ID for Field, Is Null for Operator, and False for Value.
  7. Under When to Run the Flow for Updated Records, select “Every time a record is updated and meets the condition requirements.”
  8. Under Optimize Flow, select Actions and Related Records. This triggers the flow when the record is saved.
  9. Click Save to save the Start configuration.
  10. Next, in the Flow Builder, click the plus sign (+) under the Start element and select Action.
  11. In Action Properties, search for and select the outbound message you created earlier.
  12. Give the action a Label and click Save.
  13. Now click Activate to activate the flow.
8. Go back to the recipe and select the Upsert Company in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Selecting the Agiloft CLM connection resolves the rest of the warnings in the recipe and the setup is complete.
11. Save the recipe. If you want, you can click Test recipe to test the trigger.
12. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Company records in your KB whenever Accounts are created or updated in Salesforce.
</details>

<details>
<summary>Opportunities to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Upsert Opportunity** recipe to automate creating or updating Opportunities in your KB when they’re created or updated in Salesforce.

- The actions check for a matching Opportunity and either update the existing record or create a new one. They also find the Company record for the account associated with the opportunity and link it to the Opportunity record, then update the sync details in the Salesforce record.
- To trigger the recipe, configure a Salesforce flow to send an outbound message when an Opportunity is created or updated. To prevent recipe loops, the flow includes two conditions: one to exclude updates made by the recipe and another to prevent triggering this recipe if the opportunity was already synced.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Upsert Opportunity recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Opportunity and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when an Opportunity is updated or created:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Opportunity as the Object.
  5. Trigger the flow when a record is created or updated.
  6. Now, set entry conditions to prevent recipe loops:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the first condition, select Last Modified By ID for Field and Does Not Equal for Operator.
    3. For Value, enter the Salesforce ID of the Agiloft CLM integration user. To get the ID, open the user’s Lightning record page, then copy the ID from the URL.
    4. Now click Add Condition.
    5. For the second condition, select Agiloft Company ID for Field, Is Null for Operator, and False for Value.
  7. Under When to Run the Flow for Updated Records, select “Every time a record is updated and meets the condition requirements.”
  8. Select Actions and Related Records under Optimize Flow. This triggers the flow when the record is saved.
  9. Click Save to save the Start configuration.
  10. Next, in the Flow Builder, click the plus sign (+) under the Start element and select Action.
  11. In Action Properties, search for and select the outbound message you created earlier.
  12. Give the action a Label and click Save.
  13. Now click Activate to activate the flow.
8. Go back to the recipe and select the Search Opportunity in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Selecting the Agiloft CLM connection resolves the rest of the warnings in the recipe and the setup is complete.
11. Save the recipe. If you want, you can click Test recipe to test the trigger.
12. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Opportunity records in your KB whenever an Opportunity is created or updated in Salesforce.
</details>

<details>
<summary>Contracts to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Upsert Contract** recipe to create or update Contract records in Agiloft CLM when Agiloft Contracts are created or updated in Salesforce. 

- The recipe is triggered when an outbound message is received. You set up the message and a flow to send it whenever an Agiloft Contract is created or updated.
- If the account or opportunity associated with the contract hasn’t been synced to Agiloft CLM, the actions create new Company or Opportunity records, then create or update the Contract and update the sync details in the Salesforce record.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Upsert Contract recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Agiloft Contract and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when an Agiloft Contract is created or updated:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Agiloft Contract as the Object.
  5. Trigger the flow when a record is created or updated.
  6. Now, set an entry condition to prevent recipe loops:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the condition, select Last Modified By ID for Field and Does Not Equal for Operator.
    3. For Value, enter the Salesforce ID of the Agiloft CLM integration user. To get the ID, open the user’s Lightning record page, then copy the ID from the URL.
  7. Under When to Run the Flow for Updated Records, select “Every time a record is updated and meets the condition requirements.”
  8. Select Actions and Related Records under Optimize Flow. This triggers the flow when the record is saved.
  9. Click Save to save the Start configuration.
  10. Next, to prevent updates made by the attachment and signature agreement recipes from triggering unnecessary contract sync jobs for this recipe, add a decision element to the flow and configure it to send the outbound message only if an Agiloft Contract is created or a synced field changes. To configure the decision:
    1. In the Flow Builder, click the plus sign (+) under the Start element and select Decision.
    2. For the Label, enter “Synced Field Changes?”. The API Name is set to Synced_Field_Changes.
    3. For Outcome Label, enter Yes. Outcome API Name is also set to Yes.
    4. For Condition Requirements to Execute Outcome, select Any Condition Is Met (OR).
    5. Next create a condition for each row in the [Decision conditions reference](#decision_conditions) table below. The table lists the Resource, Operator, and Value for each condition. To set the Resource value, you can copy the text in the Resource column and paste it into the Resource field in Salesforce. When you click out of the field,
    6. After adding the conditions, leave “If the condition requirements are met” selected under When to Execute Outcome and save the decision.
  11. Now, in the Flow Builder, click the plus sign (+) under the Yes element for the decision and select Action.
    1. In Action Properties, search for and select the outbound message you created earlier.
    2. Give the action a Label and click Save.
  12. In the Flow Builder, click the Default Outcome element under the decision. Enter No for the Label and click Save. The image below shows the elements in the completed flow.
  13. Finally, click Activate to activate the flow.
8. Go back to the recipe and select the Upsert Company in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Selecting the Agiloft CLM connection resolves the rest of the warnings in the recipe and the setup is complete.
11. Save the recipe. If you want, you can click Test recipe to test the trigger.
12. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Contract records in your KB when Agiloft Contracts are created or updated in Salesforce.

> Macro (anchor)

**Decision conditions reference**

| **Field** | **Resource** | **Operator** | **Value** |
| --- | --- | --- | --- |
| New record check | {!$Record__Prior.Id} | Is Null | True |
| Contract Title | {!$Record.AGI_CLM__Contract_Title__c} | Is Changed | True |
| Contract Type | {!$Record.AGI_CLM__Contract_Type__c} | Is Changed | True |
| Contract Start Date | {!$Record.AGI_CLM__Contract_Start_Date__c} | Is Changed | True |
| Contract End Date | {!$Record.AGI_CLM__Contract_End_Date__c} | Is Changed | True |
| Contract Term Months | {!$Record.AGI_CLM__Contract_Term_Months__c} | Is Changed | True |
| Status | {!$Record.AGI_CLM__Status__c} | Is Changed | True |
| Description | {!$Record.AGI_CLM__Description__c} | Is Changed | True |
| Cost Type | {!$Record.AGI_CLM__Cost_Type__c} | Is Changed | True |
| Standard or 3rd Party Paper | {!$Record.AGI_CLM__Standard_or_3rd_Party_Paper__c} | Is Changed | True |
| Agiloft Contract Name | {!$Record.Name} | Is Changed | True |
| Contract Escalated | {!$Record.AGI_CLM__Contract_Escalated__c} | Is Changed | True |
| Resubmit Requested | {!$Record.AGI_CLM__Resubmit_Requested__c} | Is Changed | True |
| Signer's Email | {!$Record.AGI_CLM__Signer_Email__c} | Is Changed | True |
| Signer's Name | {!$Record.AGI_CLM__Signer_Name__c} | Is Changed | True |
| Account | {!$Record.AGI_CLM__Account__c} | Is Changed | True |
| Opportunity | {!$Record.AGI_CLM__Opportunity__c} | Is Changed | True |
| Associated Quote | {!$Record.Associated_Quote__c} | Is Changed | True |
| Owner ID | {!$Record.OwnerId} | Is Changed | True |
| Agiloft Contract Management ID | {!$Record.AGI_CLM__Agiloft_Contract_Management_ID__c} | Is Changed | True |
| Agiloft Last Sync | {!$Record.AGI_CLM__Agiloft_Last_Sync__c} | Is Changed | True |
| Agiloft Sync Error | {!$Record.AGI_CLM__Agiloft_Sync_Error__c} | Is Changed | True |
| Integration Hub Sent Flag | {!$Record.AGI_CLM__Integration_Hub_Sent__c} | Is Changed | True |
| Contract Link | {!$Record.AGI_CLM__Contract_Link__c} | Is Changed | True |
| Message | {!$Record.AGI_CLM__Message__c} | Is Changed | True |
</details>

<details>
<summary>Contract attachments to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Contract Attachment** recipe to upload contract documents to your KB when files are added to Agiloft Contracts.

- This recipe is dependent on the Salesforce to Agiloft Upsert Contract recipe. It only syncs attachments for Agiloft Contracts that are synced with your KB.
- The actions download the attachments from Salesforce and attach them to the appropriate Contract in your KB.
- The recipe is triggered when an outbound message is received. You set up the message and a flow to send it whenever an attachment is added to an Agiloft Contract record.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Contract Attachment recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Agiloft Contract and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when an attachment is added to an Agiloft Contract record:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Agiloft Contract as the Object.
  5. Trigger the flow when a record is updated.
  6. Now, set an entry condition so the flow only runs when a file is uploaded to an Agiloft Contract record:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the condition, enter “Files Ready for Integration Hub” as the Field, select Equals for the Operator, and select True for the Value.
    3. Under When to Run the Flow for Updated Records, select “Only when a record is updated to meet the condition requirements.”
  7. Under Optimize Flow, select Actions and Related Records. This triggers the flow when the updated record is saved.
  8. Click Save to save the Start configuration.
  9. Next, in the Flow Builder, click the plus sign (+) under the Start element and select Action.
  10. In Action Properties, search for and select the outbound message you created earlier.
  11. Give the action a Label and click Save.
  12. Now click Activate to activate the flow.
8. Go back to the recipe and select the Upload Attachment into Contract in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Save the recipe. If you want, you can click Test recipe to test the trigger.
11. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to upload new files to Contract records whenever files are uploaded to Agiloft Contracts.
</details>

<details>
<summary>Contract tasks to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Upsert Task** recipe to create or update Tasks in your KB when Agiloft Tasks are created or updated in Salesforce.

- This recipe is dependent on the Salesforce to Agiloft Upsert Contract recipe. It only syncs tasks for Agiloft Contracts that are synced with your KB.
- The recipe is triggered when an outbound message is received. You set up the message and a flow to send it whenever an Agiloft Task is created or updated.
- The actions check for a matching Task and either update the existing record or create a new one. They also find the team assigned to the task and link it to the record, then update the sync details in Salesforce.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Upsert Task recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Agiloft Tasks and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when an Agiloft Task record is created or updated:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Agiloft Tasks as the Object.
  5. Trigger the flow when a record is created or updated.
  6. Now, set an entry condition to prevent recipe loops:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the condition, select Last Modified By ID for Field and Does Not Equal for Operator.
    3. For Value, enter the Salesforce ID of the Agiloft CLM integration user. To get the ID, open the user’s Lightning record page, then copy the ID from the URL.
  7. Under When to Run the Flow for Updated Records, select “Every time a record is updated and meets the condition requirements.”
  8. Select Actions and Related Records under Optimize Flow. This triggers the flow when the record is saved.
  9. Click Save to save the Start configuration.
  10. Next, in the Flow Builder, click the plus sign (+) under the Start element and select Action.
  11. In Action Properties, search for and select the outbound message you created earlier.
  12. Give the action a Label and click Save.
  13. Now click Activate to activate the flow.
8. Go back to the recipe and select the Search Team in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Selecting the Agiloft CLM connection resolves the rest of the warnings in the recipe and the setup is complete.
11. Save the recipe. If you want, you can click Test recipe to test the trigger.
12. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Task records in your KB whenever an Agiloft Task is created or updated in Salesforce.
</details>

<details>
<summary>Adobe Sign Agreements to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Upsert Adobe Sign Agreement** recipe to create or update Adobe Sign Agreement records in your KB when Signature Agreements are created or updated in Salesforce.

- This recipe is dependent on the Salesforce to Agiloft Upsert Contract recipe. It only syncs agreements for Agiloft Contracts that are synced with your KB.
- The recipe is triggered when an outbound message is received. You set up the message and a flow to send it whenever a Signature Agreement is created or updated in Salesforce.
- The actions retrieve the related contract’s Agiloft Contract Management ID, check for a matching Adobe Sign Agreement, update the existing record or create a new one, then update the sync details in the Salesforce record.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Upsert Adobe Sign Agreement recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Signature Agreements and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when a Signature Agreement record is created or updated:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Signature Agreements as the Object.
  5. Trigger the flow when a record is created or updated.
  6. Now, set an entry condition to prevent recipe loops:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the condition, select Last Modified By ID for Field and Does Not Equal for Operator.
    3. For Value, enter the Salesforce ID of the Agiloft CLM integration user. To get the ID, open the user’s Lightning record page, then copy the ID from the URL.
  7. Under When to Run the Flow for Updated Records, select “Every time a record is updated and meets the condition requirements.”
  8. Select Actions and Related Records under Optimize Flow. This triggers the flow when the record is saved.
  9. Click Save to save the Start configuration.
  10. Next, in the Flow Builder, click the plus sign (+) under the Start element and select Action.
  11. In Action Properties, search for and select the outbound message you created earlier.
  12. Give the action a Label and click Save.
  13. Now click Activate to activate the flow.
8. Go back to the recipe and select the Upsert Adobe Sign Agreement in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Selecting the Agiloft CLM connection resolves the rest of the warnings in the recipe and the setup is complete.
11. Save the recipe. If you want, you can click Test recipe to test the trigger.
12. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Adobe Sign Agreement records in your KB whenever a Signature Agreement is created or updated in Salesforce.
</details>

<details>
<summary>Adobe Sign Agreement attachments to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Adobe Sign Agreement Attachment** recipe to upload signature documents to your KB when files are added to Signature Agreements.

- This recipe is triggered when an outbound message is received. You set up the message and a flow to send it whenever an attachment is added to a Signature Agreement record.
- The actions download the attachments from Salesforce and upload them to the appropriate Adobe Sign Agreement in your KB.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Adobe Sign Agreement Attachment recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Signature Agreements and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when an attachment is added to a Signature Agreement record:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Signature Agreement as the Object.
  5. Trigger the flow when a record is updated.
  6. Now, set an entry condition so the flow only runs when a file is uploaded to a Signature Agreement record:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the condition, enter “Files Ready for Integration Hub” as the Field, select Equals for the Operator, and select True for the Value.
  7. Under When to Run the Flow for Updated Records, select “Only when a record is updated to meet the condition requirements.”
  8. Under Optimize Flow, select Actions and Related Records. This triggers the flow when the updated record is saved.
  9. Click Save to save the Start configuration.
  10. Next, in the Flow Builder, click the plus sign (+) under the Start element and select Action.
  11. In Action Properties, search for and select the outbound message you created earlier.
  12. Give the action a Label and click Save.
  13. Now click Activate to activate the flow.
8. Go back to the recipe and select the Upload attachment into Adobe Sign Agreement in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Save the recipe. If you want, you can click Test recipe to test the trigger.
11. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to attach new files to Adobe Sign Agreement records whenever files are uploaded to Signature Agreements.
</details>

<details>
<summary>Docusign Agreements to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Upsert Docusign Agreement** recipe to create or update Docusign Envelope records in your KB when Signature Agreements are created or updated in Salesforce.

- This recipe is triggered when an outbound message is received. You set up the message and a flow to send it whenever a Signature Agreement is created or updated in Salesforce.
- The actions retrieve the related contract’s Agiloft Contract Management ID, check for a matching Docusign Envelope, update the existing record or create a new one, then update the sync details in the Salesforce record.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Upsert Docusign Agreement recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Signature Agreements and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when a Signature Agreement record is created or updated:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Signature Agreements as the Object.
  5. Trigger the flow when a record is created or updated.
  6. Now, set an entry condition to prevent recipe loops:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the condition, select Last Modified By ID for Field and Does Not Equal for Operator.
    3. For Value, enter the Salesforce ID of the Agiloft CLM integration user. To get the ID, open the user’s Lightning record page, then copy the ID from the URL.
  7. Under When to Run the Flow for Updated Records, select “Every time a record is updated and meets the condition requirements.”
  8. Select Actions and Related Records under Optimize Flow. This triggers the flow when the record is saved.
  9. Click Save to save the Start configuration.
  10. Next, in the Flow Builder, click the plus sign (+) under the Start element and select Action.
  11. In Action Properties, search for and select the outbound message you created earlier.
  12. Give the action a Label and click Save.
  13. Now click Activate to activate the flow.
8. Go back to the recipe and select the Upsert DocuSign Envelope in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Save the recipe. If you want, you can click Test recipe to test the trigger.
11. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Docusign Envelope records in your KB whenever a Signature Agreement is created or updated in Salesforce.
</details>

<details>
<summary>Docusign Agreement attachments to Agiloft CLM</summary>

Use the **Salesforce to Agiloft Docusign Agreement Attachment** recipe to upload signature documents to your KB when files are added to Signature Agreements.

- This recipe is dependent on the Salesforce to Agiloft Upsert Docusign Agreement recipe. It only syncs attachments for Signature Agreements that are synced with your KB.
- The recipe is triggered when an outbound message is received. You set up the message and a flow to send it whenever an attachment is added to a Signature Agreement record.
- The actions download the attachments from Salesforce and upload them to the appropriate Docusign Envelope record in your KB.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Salesforce to Agiloft Docusign Agreement Attachment recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Salesforce connection to use for this recipe.
5. Now, on the Setup tab, copy the Endpoint URL.
6. Using the Endpoint URL you copied, set up an outbound message in Salesforce:
  1. In the Agiloft for Salesforce app, go to Setup, then go to Outbound Messages under Workflow Actions.
  2. Click New Outbound Message.
  3. On the Select object screen, select Signature Agreements and click Next.
  4. On the edit screen, give the message a unique name.
  5. In the Endpoint URL field, paste the Endpoint URL you copied from the recipe.
  6. In the User to send as field, select the Agiloft CLM integration user.
  7. Next, move all fields from Available Fields to Selected Fields so the message includes the fields the recipe expects.
  8. Click Save to save the message.
7. Now that the outbound message is set up, follow these steps to create a flow that sends the message when an attachment is added to a Signature Agreement record:
  1. In Setup, go to Flows under Process Automation.
  2. Click New Flow.
  3. On the New Automation screen, select Record-Triggered Flow.
  4. In the Flow Builder under Configure Start, select Signature Agreement as the Object.
  5. Trigger the flow when a record is updated.
  6. Now, set an entry condition so the flow only runs when a file is uploaded to a Signature Agreement record:
    1. Under Set Entry Conditions, select All Conditions Are Met (AND) from the Condition Requirements drop-down list.
    2. For the condition, enter “Files Ready for Integration Hub” as the Field, select Equals for the Operator, and select True for the Value.
  7. Under When to Run the Flow for Updated Records, select “Only when a record is updated to meet the condition requirements.”
  8. Under Optimize Flow, select Actions and Related Records. This triggers the flow when the updated record is saved.
  9. Click Save to save the Start configuration.
  10. Next, in the Flow Builder, click the plus sign (+) under the Start element and select Action.
  11. In Action Properties, search for and select the outbound message you created earlier.
  12. Give the action a Label and click Save.
  13. Now click Activate to activate the flow.
8. Go back to the recipe and select the Upload attachment into Docusign Envelope in Agiloft step.
9. On the Connection tab, select the Agiloft CLM connection to use for this recipe. You don’t need to configure any settings on the Setup tab.
10. Save the recipe. If you want, you can click Test recipe to test the trigger.
11. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to attach new files to Docusign Envelope records whenever files are uploaded to Signature Agreements.
</details>

# Sync Agiloft CLM data to Salesforce

This section provides instructions for activating each of the recipes that sync data from Agiloft CLM to Salesforce. To get started, select what you want to do:

<details>
<summary>Contract updates to Salesforce</summary>

Use the **Agiloft to Salesforce Update Contract** recipe to update Agiloft Contracts in Salesforce when Contracts are updated in Agiloft CLM.

- This recipe is dependent on the Salesforce to Agiloft Upsert Contract recipe. It only updates Agiloft Contracts that are synced with your KB.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Agiloft to Salesforce Update Contract recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Agiloft CLM connection to use for this recipe.
5. Next, select the Update Agiloft Contract in Salesforce step. On the Connection tab, select the Salesforce connection to use.
6. Save the recipe. If you want, you can click Test recipe to test the trigger.
7. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to update the Agiloft Contract in Salesforce whenever a synced Contract is updated in Agiloft CLM.
</details>

<details>
<summary>Approvals to Salesforce</summary>

Use the **Agiloft to Salesforce Upsert Approval** recipe to create or update Agiloft Approval records in Salesforce when Approvals are created or updated in your KB.

- This recipe is dependent on the Salesforce to Agiloft Upsert Contract recipe. It only syncs approvals for Agiloft Contracts that are synced with your KB.
- The actions check for a matching Agiloft Approval record in Salesforce and either update the matching record or create a new one.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Agiloft to Salesforce Upsert Approval recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Agiloft CLM connection to use for this recipe.
5. Next, select the Upsert Agiloft Approval in Salesforce step. On the Connection tab, select the Salesforce connection to use.
6. Save the recipe. If you want, you can click Test recipe to test the trigger.
7. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update an Agiloft Approval in Salesforce whenever an approval for a synced contract is created or updated in Agiloft CLM.
</details>

<details>
<summary>Tasks to Salesforce</summary>

Use the **Agiloft to Salesforce Upsert Task** recipe to create or update Agiloft Task records in Salesforce when Tasks are created or updated in your KB.

- This recipe is dependent on the Salesforce to Agiloft Upsert Contract recipe. It only syncs tasks for Agiloft Contracts that are synced with your KB.
- The actions find the related contract in Agiloft CLM and then update the Agiloft Task record in Salesforce with the changes from your KB.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Agiloft to Salesforce Upsert Task recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Agiloft CLM connection to use for this recipe.
5. Next, select the Upsert Agiloft Task in Salesforce step. On the Connection tab, select the Salesforce connection to use.
6. Save the recipe. If you want, you can click Test recipe to test the trigger.
7. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Agiloft Tasks in Salesforce when Tasks are created or updated in Agiloft CLM.
</details>

<details>
<summary>Adobe Sign Agreement updates to Salesforce</summary>

Use the **Agiloft to Salesforce Update Adobe Sign Agreement** recipe to update Signature Agreement records in Salesforce when Adobe Sign Agreements are updated in your KB.

- This recipe is triggered when a synced Adobe Sign Agreement is updated in your KB.
- The actions find the related contract in Agiloft CLM and then update the Signature Agreement in Salesforce with the changes from your KB.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Agiloft to Salesforce Update Adobe Sign Agreement recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Agiloft CLM connection to use for this recipe.
5. Next, select the Update Signature Agreement in Salesforce step. On the Connection tab, select the Salesforce connection to use.
6. Selecting the Salesforce connection resolves the rest of the warnings and the setup is complete.
7. Save the recipe. If you want, you can click Test recipe to test the trigger.
8. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to update the Signature Agreement in Salesforce whenever a synced Adobe Sign Agreement is updated in Agiloft CLM.
</details>

<details>
<summary>Adobe Sign Recipients to Salesforce</summary>

Use the **Agiloft to Salesforce Upsert Adobe Sign Recipient** recipe to create or update Signature Recipient records in Salesforce when Adobe Sign Recipients are created or updated in your KB.

- This recipe is triggered when an Adobe Sign Recipient record is created or updated in your KB.
- The actions find the related contract and Adobe Sign Agreement record in Agiloft CLM, check for a matching Signature Recipient in Salesforce, and either update the existing record or create a new one.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Agiloft to Salesforce Upsert Adobe Sign Recipient recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Agiloft CLM connection to use for this recipe.
5. Next, select the Upsert Adobe Sign Recipient in Salesforce step. On the Connection tab, select the Salesforce connection to use.
6. Save the recipe. If you want, you can click Test recipe to test the trigger.
7. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Signature Recipients in Salesforce when Adobe Sign Recipients are created or updated in Agiloft CLM.
</details>

<details>
<summary>Docusign Agreement updates to Salesforce</summary>

Use the **Agiloft to Salesforce Update Docusign Agreement** recipe to update Signature Agreement records in Salesforce when Docusign Envelopes are updated in your KB.

- This recipe is triggered when a synced Docusign Envelope is updated in your KB.
- The actions find the related contract in Agiloft CLM and then update the Signature Agreement in Salesforce with the changes from your KB.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Agiloft to Salesforce Update Docusign Agreement recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Agiloft CLM connection to use for this recipe.
5. Next, select the Update Signature Agreement in Salesforce step. On the Connection tab, select the Salesforce connection to use.
6. Selecting the Salesforce connection resolves the rest of the warnings in the recipe and the setup is complete.
7. Save the recipe. If you want, you can click Test recipe to test the trigger.
8. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to update the Signature Agreement in Salesforce whenever a synced Docusign Envelope is updated in Agiloft CLM.
</details>

<details>
<summary>Docusign Recipients to Salesforce</summary>

Use the **Agiloft to Salesforce Upsert Docusign Recipient** recipe to create or update Signature Recipient records in Salesforce when Docusign Recipients are created or updated in your KB.

- This recipe is triggered when a Docusign Recipient record is created or updated in your KB.
- The actions find the related Contract and Docusign Envelope in Agiloft CLM, search for a matching Signature Recipient record in Salesforce, and either update the existing record or create a new one.

To set up the recipe:

1. Log in to your KB as the integration user.
2. Go to **Setup > Integration Hub** and go to the Recipes tab.
3. Find the Agiloft to Salesforce Upsert Docusign Recipient recipe and open it for editing.
4. Click the trigger step to open the configuration panel. On the Connection tab, select the Agiloft CLM connection to use for this recipe.
5. Next, select the Upsert Signature Recipient in Salesforce step. On the Connection tab, select the Salesforce connection to use.
6. Save the recipe. If you want, you can click Test recipe to test the trigger.
7. To activate the recipe, exit the recipe editor and click Start recipe.

The integration is now configured to create or update Signature Recipients in Salesforce when Docusign Recipients are created or updated in Agiloft CLM.
</details>

#### Related articles

> Macro (contentbylabel)