Salesforce Configuration
Moving Contacts to Likely Accounts
you can configure recruiterbolt to create a recruiterbolt event record when it sees that a salesforce lead or contact has a different employer compared to the last run there isn't a single way to achieve this the following tutorial suggests moving the salesforce contact to their new company by changing the account lookup of the contact to the account in the salesbolt event's likely account (if populated) and also update the email address (if populated) this approach will also move salesforce tasks to the moved contact, and thus may also remove the communication history from the old account to the new account hence, it's unsuitable if you want to keep your communication history associated with the relevant account click on setup , search for flows in the quick find search box and click on new flow select record triggered flow and click on create set the following start configurations select salesbolt event as an object and select a record is updated in configure trigger set entry conditions as select all conditions are met (and) under condition requirements, salesbolt likely account c is not empty and salesbolt type c equals ‘employer change ’ select only when a record is updated to meet the condition requirements and select actions and related records under optimize the flow for and click the done button click the + symbol to add an element select update records under data give a label and select the specify conditions to identify records, and set fields individually option choose object as contact and add conditions like id (contact id) is equal to salesbolt contact c ({! $record salesbolt contact c}) now update the field values of contact accountid with salesbolt likely accountid ({!$record salesbolt likely account r id}), email with salesbolt new email c ({!$record salesbolt new email c}) ownerid with likely account ownerid({!$record likely account r ownerid}) click the done button save the flow by clicking the save button you will be required to set a flow label , flow api name , and, optionally, a description click on the activate button to activate the flow