Customer Onboarding Automation
Created by IWConnect This pattern is a customer onboarding use case that creates an automated data flow between a customer portal application and the Salesforce CRM platform, and then back to the customer portal application. Whether to kick off the customer experience journey or to initiate a lead management process, a common first step is to capture the first set of customer engagement information into a CRM system and create a record or opportunity. Configuration See this video for more information: Customer Onboarding Automation with SnapLogic - YouTube Sources: Customer Portal Targets: Salesforce Snaps used: REST Get, Union, Mapper, Salesforce Create Downloads 01_p1_CreateLead.slp (8.5 KB)
Sync new/updated lead from Microsoft Dynamics CRM to Marketo
Created by @mthammareddy For a lead created or updated in Microsoft Dynamics CRM, SnapLogic searches for a matching lead in Marketo by email address. If no matching lead is found in Marketo, SnapLogic creates a new lead. If a matching lead is found in Marketo, SnapLogic updates that lead. Configuration You will need to define the following pipeline parameters: authorization, in the form of Bearer xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:xx endpoint, in the form of https://xxx-xxx-xxx.mktorest.com Sources: Microsoft Dynamics CRM Lead Targets: Marketo Lead Snaps used: Dynamic CRM Read, Filter, Mapper, JSON Generator, REST Post Downloads Microsoft_CRM_Lead_Record_Marketo.slp (9.9 KB)
NetSuite Case to ServiceNow Incident
Created by @tlui This pipeline looks for NetSuite Cases in past 24 hours and brings them to ServiceNow. The pipeline attempts to bring the email of the NetSuite user but if none is found, it is defaulted for ServiceNow. Customers may want to use the NetSuite Contact to ServiceNow User pattern in conjunction with this to ensure ServiceNow Users exist for a corresponding NetSuite Contact. Configuration This pattern was created using NetSuite WSDL: 2018, Release 1 and ServiceNow London Version. The NetSuite query range may be configured. The head within the pipeline may be configured or removed to allow for a larger number of records through once the pattern is fully tested. Sources: NetSuite Issue Targets: ServiceNow Incident Snaps used: NetSuite Search, Mapper, JSON Splitter, Head, Copy, NetSuite Get, Join, ServiceNow Insert Downloads NetSuite Case to ServiceNow Incident.slp (19.1 KB)
Move Salesforce Opportunity to NetSuite Sales Order
Created by @dshen This pipeline pattern will take a closed Salesforce opportunity and create a Sales Order in NetSuite, and then update Salesforce with the NetSuite ID. Configuration The pipeline will take a closed Salesforce opportunity ID as the pipeline parameter. The pipeline will assume the Salesforce product and NetSuite item has been synchronized, and the NetSuite item internal ID is stored in each Salesforce product. The pipeline will create a new NetSuite customer if the Salesforce Opportunity Account is not already created. The pipeline will create the NetSuite Sales Order based on the approved Opportunity Quote. Each Salesforce Quote Line Item will create a NetSuite SalesOrder Line Item. Sources: Salesforce Opportunity, Account, Quote, Quote Line Items Targets: NetSuite Customer, Sales Order Snaps used: Salesforce SOQL, NetSuite Create, Salesforce Update, Mapper, Router, Join, Group By Fields, JSON Splitter Downloads SFDC Opportunity to NS SalesOrder.slp (36.8 KB)
