1 of 7

Enate Integration Services powered by SnapLogic

Enate has teamed up with one of the leading iPaaS vendors SnapLogic to offer iPaaS as part of the Enate platform for clients that do not already have their own iPaaS, or are seeking a more business user friendly solution.

Enate Integration Services provides the full SnapLogic capabilities to Enate customers under a single agreement with Enate. It's a separate module of Enate and can be purchased alongside the core product, with preferred options and prices through Enate's partnership with SnapLogic. If you're interested in using Enate Integration Services, speak to your Account Manager about setting this up.

The explanations on using Enate Integration Services powered by SnapLogic are structured as follows:

SnapLogic Overview - This is your introduction to SnapLogic and how it works. Here you'll find links to SnapLogic's own articles and helpful links to get you up to speed with using it.
iPaaS Patterns - This section focuses on theory: explaining the four fundamental patterns that you can set up when using iPaaS with Enate integration Services to integrate with other systems. All use cases will fit within one of these models, or a combination of them.
Build your Pipeline - Enate Integration Pattern 1 - Once you know how to use SnapLogic, and you know what patterns can be built, you're ready to create end-to-end integrations with Enate. This section takes you on a detailed walkthrough of a real-world business process solution for Pattern 1: Walk through how to set up a SnapLogic Pipeline to work with Enate and a Third Party system.
Enate Integration Services FAQs - further information about how to set up & use Enate Integration Services with SnapLogic
Resources - a library of useful resources like Pipelines & Snaps for you to use as you build process solutions with Enate Integration Services. This list of downloadable resources will grow over time.

SnapLogic Overview

is a system that allows for different systems to communicate with one another. It facilitates a number of different tasks such as data retrieval and system updating. Enate has teamed up with SnapLogic to offer Enate Integration Service, providing an iPaaS solution as part of the Enate platform for clients that do not already have their own iPaaS, or are seeking a more business user friendly approach.

Key SnapLogic Information Links

- SnapLogic's own online help, answering questions on how to build, manage, and troubleshoot your integrations.
- where users can discuss, learn, and share insights
- online training platform. Access available upon purchase of Enate Integration Services. (Please note this is different from Enate Academy).
- links to a number of walkthroughs showing how to build solutions for various industries or functions.
- an in-built AI assistant that helps create & analyze pipelines & snaps, answer your questions, and generally cut the time taken to build processes.

How can I get started using Enate Integration Services?

If you're interested in using Enate Integration Services, speak to your Account Manager about setting this up.

What's included?

When you purchase Enate Integration Services you'll get:

Access to a SnapLogic Intelligent Integration Platform (IIP) environment
. Snaps are the building blocks of a pipeline, your processes in SnapLogic. By default, the Snap Catalog contains a set of Core Snaps available to all users. Premium Snaps, custom-made for accessing popular platforms such SAP, Salesforce etc. can also be purchased - speak to your Account Manager if this of interest. Check out the for more information (Core snaps are marked here).
Access for 5 people to . Please note: This access is available for 6 weeks from the day of your request, so make sure to start using your SnapLogic Academy account as soon as you are given access.

Navigating SnapLogic IIP Platform

Once you've got access to a Snaplogic account you'll be given access to the Intelligent Integration Platform

Designer Page

Manager Page

Dashboard Page

What are Pipelines and Snaps?

What Snaps do I have access to?

How to Authenticate a Snap

When you are configuring a Snap to use an API to contact a third-party software, you will need to authenticate the Snap. This is done by adding an account in the Snap settings. You also have the option to add an account via the SnapLogic manager page.

How to Validate and Execute a Pipeline

What is a Task in SnapLogic?

Monitoring your Pipelines, Tasks and Snaps

You can track the integration's (pipeline's) performance through the Enate integration service monitoring tools.

Alerts and how to set them up

Types of Alerts:

System-defined alerts: Automatically triggered based on predefined event parameters.
User-defined alerts: Configurable by Org admins for specific events.

Alert Categories:

Congestion Alerts: Notify when pipelines are queued for too long, indicating capacity issues.
Alert and Activity Log Notifications: Inform about events like pipeline execution exceeding usual limits.
User Notifications: Custom messages targeted to specific users.
Snaplex Notifications: Alerts for Snaplex events such as maintenance or upgrades.
Task Notifications: Inform about task execution occurrences.

SnapGPT

For more information, check out the dedicated article:

Using SnapGPT to help you in SnapLogic

A very useful and powerful tool that you have at your disposal in SnapLogic is their own in-built .

You can have SnapGPT carry out essential any and all tasks in SnapLogic. You can ask it to create or configure a specific Snap for you, identify why your pipeline may not be working or even create a pipeline from scratch for you.

You can also have SnapGPT carryout more contextual skills such as generating expressions or SQLs. SnapGPT can also answer any questions you have about using SnapLogic and retrieve any useful SnapLogic documentation.

iPaaS Patterns

When using Enate with iPaaS there are four different basic ‘patterns’ that you can use. All use cases fit within one of these models.

There are a few integration patterns to consider, and you can choose one or all based on your use cases. Enate's clients currently perform integration at their end using their own iPaaS tool. However, we are researching a new tool that Enate can offer to its clients, but the coding, maintenance and support will be the responsibility of the clients themselves.

Pattern 1 - Enate Workflow Updates External Application

When should I use this pattern? - This is the most common integration pattern. Use it when in this pattern when you want to update or get data from an external system at a known point in an Enate Workflow.

How does it work? Enate calls iPaaS to start a recipe that will update an external application.

Trigger: Enate workflow task calls the iPaaS API to start the recipe.
iPaaS: Upon receiving the Enate call, transform the data and send it to the external application via API call.
Receiver: External application gets new information and data is updated / action is taken.
Optional: Enate can either wait for the iPaaS to call back confirming that the other application has completed the updates, or just move on with the process.

Pattern 1 use cases:

Upon creation of a new Deal in your sales department, you want to grab data from HubSpot to help with onboarding.
At the end of an onboarding process, you want to upload the signed employee contract to the HR system.
At the start of the Accounts Payable process, you want to get the relevant Purchase Order details from the ERP system into Enate.

Walkthrough creating Pattern 1

Look at how to build your own example of this pattern using Enate, a 3rd party system, and Enate Integration Services (SnapLogic):

Pattern 2 - Synchronize Data in Enate on External Events

When should I use this pattern? You should use this pattern when you want data to be updated or action taken in Enate whenever something specific happens in an external system (i.e. there is a specific event in that system).

How does it work? - In this pattern, events in an external application will fire webhooks triggering the iPaaS to execute a recipe and update Enate.

Trigger: Data is changed in an external application causing a webhook to be triggered.
iPaaS: Monitor the external application by subscribing to the webhook related to this event and call Enate API with an update when it happens.
Receiver: Enate receives new information over the API and updates the system or takes action depending on the API called by the iPaaS.

Pattern 2 use cases:

A new deal is created in Salesforce, it needs to trigger a customer onboarding workflow in Enate.
A new employee is onboarded to the HR system and they need to be set up as a User in Enate.
A new message is received in a client web Portal and it needs to notify the Enate user processing that customer’s case.
The list of Exception Types in SAP needs to be synchronised into Enate so that it can be shown in a Custom Card.

Pattern 3 - Synchronize data in External Systems on Events in Enate

When should I use this pattern? This is very similar to Pattern 2, but in this case you want data that is mastered in Enate to be automatically synchronised to the 3rd party system.

How does it work? The flow is identical to Pattern 2 but with the systems reversed i.e. Listen to Enate webhook and update the external system.

Pattern 3 use cases:

A new email is received in Enate and it needs to be uploaded to a client portal so that it is visible online for the client.

Pattern 4 - Transform Data within an Enate Process

When should I use this pattern? This makes use of some of the additional feature of iPaaS systems. Because system integration is about transforming the data from System A to fit the data in System B, iPaaS are very good at data transformation. You can make use of this feature by sending data form Enate up to the iPaaS system and using a pattern to transform the data.

How does it work? In this pattern, Enate data is transformed into a new format but does not necessarily need to connect to a third-party system.

Trigger: Enate workflow task calls the iPaaS API to start the pattern.
iPaaS: on Enate call, transform the data and send it back via update API.
Receiver: Enate gets new information and updates it.

Pattern 4 use cases:

A spreadsheet received form a client containing new payroll data needs to be transformed so that it can be automatically uploaded to a Payroll system.

Build your Pipeline - Enate Integration Pattern 1

This walkthrough will take you through how to integrate an external system into Enate using our Enate Integration Services iPaaS approach powered by Snaplogic. This will demonstrate one of the four standard patterns which you can achieve with iPaaS, specifically where we want to update or get data from an external system at a known point in an Enate Workflow. The shortcuts to the main sections for building this pattern are:

Prerequisites

What you'll need in order to connect Enate with 3rd party systems using Enate Integration Services:

Enate Access – An Enate instance where you have Builder-level admin access
Enate Integration Services (Snaplogic) Access –
Familiarization with Snaplogic – see the for this.
A 3rd Party system (in this example HubSpot), where you have configuration-level admin access.

Process Overview

We will build a standard Enate Case process which gets created each time there is a new business Deal in our are of the business. Part of this case calls an external system (we'll use HubSpot here) to bring data into the Enate Case process. This could just as easily be e.g. SAP, Salesforce etc.

This will be done by calling out to Enate Integration Services (powered by Snaplogic) which will grab the data from HubSpot, update the Enate Action, and then confirm that the API call is complete. The main activities in the end-to-end flow are as follows:

In Enate: External API Call – a ‘Trigger External API’ action is placed into the Case flow in Builder. This calls out to Enate Integration Services (Snaplogic) to run a specific Pipeline. Then the SnapLogic pipeline...
Calls the 3rd party System (HubSpot) – In Snaplogic a pipeline is called, this will make a call out to the 3rd party system, in this case HubSpot.
Obtains Data from HubSpot - The incoming information passed into HubSpot will allow the relevant values to be identified and sent back to Snaplogic.
Generates a Bearer Token for Accessing Enate - while this part isn't strictly necessary to complete the final snap in the pipeline (which will actually use a Callback URL for authorization instead in this example), knowing how to generate a Bearer Token for getting authorized access to your Enate system will be essential for your pipeline work going forward.
Updates Enate Data Fields & Confirms Completion of Enate Action – The updated field values are sent back to the Action in Enate, ‘Trigger External API’ action in Enate is marked as complete, allowing the Enate Case to move onto the next part of the Enate flow.

Configuration in Enate

Create Case, Custom Fields, Custom Card

Steps for the required Enate configuration are as follows:

In your Builder environment, create a new Case process for New Deals.
In conjunction, create a series of new Custom Data fields and a Custom Card for them to show on.

Set Field values as follows:

Link the Custom Card to the Case configuration.
Add a new Action at the relevant point in your Case process. You may need to create a brand new Action. Give it a sensible name, and choose type ‘Trigger External API Action’.
You’ll need to set the following information as part of the detailed Action settings:

Setting the API Integration URL & Bearer Token in your Enate API Action

The API Integration URL you enter here will call a specific Pipeline in Enate Integration Services (Snaplogic). To add that url in this Enate action’s config, you’ll first have to create that Pipeline in Snaplogic. In addition to pointing this action at the right Snaplogic location and instance, the Pipeline will also require some authentication before it will allow the action to access it. This is done by adding in a ‘Bearer Token’ as a variable at the end of the url. The format of the url is:

https://[snaplogic pipeline link] + ‘?bearer_token=’ + [the pipeline’s bearer token’], e.g.

Once you’ve completed your steps to create your pipeline and token, you will need to circle back round to here to complete your action configuration (at which point you may then be ready to test the end to end process).

Additional Action Level Configuration to complete

Set an Allocation rule to route the Action back to the work item starter – this would be used in the situation where the action times out, to provide a ‘human in the loop’ to deal with any issues.

Snaplogic Pipeline Construction

Pipeline Overview

Here is downloadable example of this Pipeline:

Walk-through of each Snap

Create Pipeline & Add Snap 1 - JSON Parser

Snap 2 - HubSpot Bulk Read (Accessing your 3rd Party System)

Snap 3 - HTTP Client - Get Open Deals from HubSpot (3rd Party System)

Snap 4 - HTTP Client - Get Enate Bearer Token

This snap is an essential for almost all pipelines you may build, as it gets a Bearer Token from Enate which can be used in many of the subsequent Snaps you build which need to Access Enate*. *the other way to get authorization is to use the 'Callback URL' which forms part of Enate's external API call out to Snaplogic)

Snap 5 - HTTP Client - Update Action & Complete

This snap updates the Enate Action which called the Pipeline, sending the values grabbed from HubSpot and mapping them to the Enate fields to be updated. It also tells Enate that the action is complete and it can move on.

Note that rather than use the Bearer Token approach to authorize access to Enate here, we're instead going to reference the 'Callback URL' which would be supplied to Snaplogic by the calling Enate 'Trigger External API' action.

As a sample of the kind of code you'd be writing here to update fields back in Enate, here is the code used in the above snap to update the calling action with values from the 3rd party HubSpot system:

{
  "DataFields": {
    "DealName": $original.entity.deals[0].deal_name,
    "DealType": $original.entity.deals[0].deal_type,
    "Priority": $original.entity.deals[0].priority,
    "DealAmount": $original.entity.deals[0].deal_amount,
    "DealOwner": $original.entity.deals[0].deal_owner,
   "CreatedDate": $original.entity.deals[0].created_date,
   "CloseDate": $original.entity.deals[0].close_date
  },
 "Success": true
}

Once this Pipeline is created, it's time to circle back to the Enate configuration to tell the Enate Action which Pipeline to call from SnapLogic. This is done by creating a Triggered Task in SnapLogic...

How do I get Enate to call the SnapLogic Pipeline?

Create a Triggered Task & add url into Enate Action Config

To tell Enate how to call this pipeline we need to:

create a Triggered Task in SnapLogic
Paste the url for this Triggered Task back into the configuration settings for the Enate Action, along with an additional variable for a SnapLogic Bearer Token.

Enate Integration Services FAQs

Do I get access to SnapLogic training material? - SnapLogic Academy

As an Enate Integration Service customer, you have access to a Learning Management System (LMS) where you can take the online beginner course on the SnapLogic platform. Each Enate customer receives five named seats on this platform for 30 days.

The course is self-paced for four weeks and should take a few hours per week to complete. We will also provide you with a sandbox environment where you can create your pipeline and gain hands-on experience.

The beginner course covers the following topics:

To access the LMS and the playground, please contact your support team via email, and they will provide you with all the necessary access.

ease note that the Learning Management System access is only available for 30 days. Therefore, it's important to send your request when you are ready to start, as access will automatically expire 30 days after the request date.

Can I access more SnapLogic Academy Courses?

How can I stay up to date with the latest developments to the SnapLogic platform?

How do I find out about SnapLogic updates and releases?

SnapLogic usally releases patches and updates querterly. When a quarterly release is deployed, each SnapLogic customer can decide to keep their existing version of Snaplex (Cloudplex or Groundplex) and Snap Packs for up to four weeks + two days before upgrading. This time window allows you to ensure that the new Snaplex and Snap Packs are stable and working as expected before rolling them to all your Orgs.

You can update Snaplex instances within an Org automatically by selecting the checkbox on Manager > Settings > Auto Upgrade Snaplex. This setting updates the Snaplex to the latest available version.

How can I check the status of SnapLogic's platform?

Glossary of SnapLogic Terms

Here are some key terms that are useful to know when working with SnapLogic:

Snap: Modular components that perform specific functions in a pipeline, used to connect and process data from different sources.
Pipeline: A sequence of connected Snaps that define an integration flow, where data flows from source to destination.
Snaplex: The runtime engine that processes integrations in SnapLogic.
Cloudplex: A cloud-based Snaplex managed by SnapLogic.
Groundplex: A self-managed Snaplex deployed on-premises or in a private cloud.
Designer: The graphical interface for creating and editing pipelines.
Task: A configured pipeline execution, which can be triggered or scheduled.
Ultra Task: A task that accepts streaming input.
Triggered Task: A task that can be invoked via API call.
Scheduled Task: A task that runs on a defined schedule.
Project Space: A container for organizing projects and assets.
Project: A collection of related integration assets.
Asset: Any reusable component in SnapLogic, such as pipelines, tasks, or accounts.
Snap Account: Credentials configuration for connecting to endpoints.
Control Plane: The part of the platform that manages user interfaces and asset storage.
Data Plane: The part of the platform that executes pipelines and processes data.

Resources and Links

Downloadable Resources

This section will contain a growing list of resources that you can download and use when creating pipelines in SnapLogic.

You can download an example pipeline for testing below:

Useful SnapLogic Links

- SnapLogic's own online help, answering questions on how to build, manage, and troubleshoot your integrations.
- where users can discuss, learn, and share insights.
- online training platform. Access available upon purchase of Enate Integration Services. (Please note this is different from Enate Academy).
- links to a number of walkthroughs showing how to build solutions for various industries or functions.
- an in-built AI assistant that helps create & analyze pipelines & snaps, answer your questions, and generally cut the time taken to build processes.

iPaaS Patterns

When using Enate with iPaaS there are four different basic ‘patterns’ that you can use. All use cases fit within one of these models.

Pattern 1 - Enate Workflow Updates External Application

How does it work? Enate calls iPaaS to start a recipe that will update an external application.

Trigger: Enate workflow task calls the iPaaS API to start the recipe.
iPaaS: Upon receiving the Enate call, transform the data and send it to the external application via API call.
Receiver: External application gets new information and data is updated / action is taken.
Optional: Enate can either wait for the iPaaS to call back confirming that the other application has completed the updates, or just move on with the process.

Pattern 1 use cases:

Upon creation of a new Deal in your sales department, you want to grab data from HubSpot to help with onboarding.
At the end of an onboarding process, you want to upload the signed employee contract to the HR system.
At the start of the Accounts Payable process, you want to get the relevant Purchase Order details from the ERP system into Enate.

Walkthrough creating Pattern 1

Look at how to build your own example of this pattern using Enate, a 3rd party system, and Enate Integration Services (SnapLogic):

Build your Pipeline - Enate Integration Pattern 1

Pattern 2 - Synchronize Data in Enate on External Events

How does it work? - In this pattern, events in an external application will fire webhooks triggering the iPaaS to execute a recipe and update Enate.

Trigger: Data is changed in an external application causing a webhook to be triggered.
iPaaS: Monitor the external application by subscribing to the webhook related to this event and call Enate API with an update when it happens.
Receiver: Enate receives new information over the API and updates the system or takes action depending on the API called by the iPaaS.

Pattern 2 use cases:

A new deal is created in Salesforce, it needs to trigger a customer onboarding workflow in Enate.
A new employee is onboarded to the HR system and they need to be set up as a User in Enate.
A new message is received in a client web Portal and it needs to notify the Enate user processing that customer’s case.
The list of Exception Types in SAP needs to be synchronised into Enate so that it can be shown in a Custom Card.

Pattern 3 - Synchronize data in External Systems on Events in Enate

When should I use this pattern? This is very similar to Pattern 2, but in this case you want data that is mastered in Enate to be automatically synchronised to the 3rd party system.

How does it work? The flow is identical to Pattern 2 but with the systems reversed i.e. Listen to Enate webhook and update the external system.

Pattern 3 use cases:

A new email is received in Enate and it needs to be uploaded to a client portal so that it is visible online for the client.

Pattern 4 - Transform Data within an Enate Process

How does it work? In this pattern, Enate data is transformed into a new format but does not necessarily need to connect to a third-party system.

Trigger: Enate workflow task calls the iPaaS API to start the pattern.
iPaaS: on Enate call, transform the data and send it back via update API.
Receiver: Enate gets new information and updates it.

Pattern 4 use cases:

A spreadsheet received form a client containing new payroll data needs to be transformed so that it can be automatically uploaded to a Payroll system.

SnapLogic Overview

Key SnapLogic Information Links

- SnapLogic's own online help, answering questions on how to build, manage, and troubleshoot your integrations.
- where users can discuss, learn, and share insights
- online training platform. Access available upon purchase of Enate Integration Services. (Please note this is different from Enate Academy).
- links to a number of walkthroughs showing how to build solutions for various industries or functions.
- an in-built AI assistant that helps create & analyze pipelines & snaps, answer your questions, and generally cut the time taken to build processes.

How can I get started using Enate Integration Services?

If you're interested in using Enate Integration Services, speak to your Account Manager about setting this up.

What's included?

When you purchase Enate Integration Services you'll get:

Access to a SnapLogic Intelligent Integration Platform (IIP) environment
. Snaps are the building blocks of a pipeline, your processes in SnapLogic. By default, the Snap Catalog contains a set of Core Snaps available to all users. Premium Snaps, custom-made for accessing popular platforms such SAP, Salesforce etc. can also be purchased - speak to your Account Manager if this of interest. Check out the for more information (Core snaps are marked here).
Access for 5 people to . Please note: This access is available for 6 weeks from the day of your request, so make sure to start using your SnapLogic Academy account as soon as you are given access.

Navigating SnapLogic IIP Platform

Once you've got access to a Snaplogic account you'll be given access to the Intelligent Integration Platform

Once logged in, you have three main pages, accessible from the tabs at the top of the screen. They are the , the and the .

Designer Page

The is where you create and interact with the pipelines you create and their various individual snaps. You will be able to find the complete library of snaps available to you on this page as well as carryout key pipeline tasks such as validation and pipeline comparison.

Manager Page

The page is where you you can manage everything you create or have access to within SnapLogic such as Tasks, Pipelines and Snap Packs. Manager presents all of your SnapLogic assets in a manageable manner so that you have the power to delete, edit, export, import or what ever else you need to to. This Manager page is also where you will be able to create assets such as Triggered Tasks and find out all of their relevant information and values.

Dashboard Page

The page is where you will be able to view information relating to your pipelines, tasks, snaplex, and APIs. You will be able to view their health, how long it took them to complete tasks and if any have encountered issues and failed to work.

What are Pipelines and Snaps?

A in SnapLogic is what you build when you connect multiple snaps together, defining the flow of data between different systems and applications. Putting snaps into a pipeline allows for the orchestrating of processes such as extracting, transforming and loading of data between snaps, with each snap performing a specific function within the larger .

A represents a building block that carriers out a single function when it is added to a pipeline. Different snaps are designed to carrier out such as like reading data from a source, transforming it, or writing it to a target application; essentially, each snap performs a specific task on data within a pipeline, making it easier to connect different applications and data sources without complex coding.

What Snaps do I have access to?

SnapLogic offers a diverse range of snaps organized into different based on their functionalities. The main categories include:

: These are essential snaps available to all users by default.
: Including packs for Anaplan, Birst, Google Analytics, Google Analytics 4, Splunk, SumoLogic, and Tableau.
: A wide variety of specialized snaps such as Adobe Experience Platform, Akamai, Amazon ElastiCache, AWS EC2 Utilities, Databricks Utils, Dremio, DocuSign, Microsoft Dynamics AX 2009, Reltio, BAI File Parser, MQTT, NetSuite SOAP, Eloqua, and Teamcenter.
: Including NetSuite SOAP and Eloqua Snap Packs.
(Machine Learning) Snaps: SnapLogic provides various snaps for machine learning and data science use cases, though specific Snap Packs are not detailed in the documentation I accessed.

While core snaps will be free for all users to use, most enterprise snaps will require premium snap packs to be purchased for the user. It's important to note that the available snaps may change over time as SnapLogic continues to develop and update its platform. For the most up-to-date and complete list of snaps, Check out the (Core snaps are marked here).

How to Authenticate a Snap

When you are adding an account, you will need to select a location, an account type, fill in all the required details and then you will be able to validate the authentication. For more information on how to authenticate a Snap in SnapLogic you can view the .

How to Validate and Execute a Pipeline

To and a pipeline in SnapLogic, open the pipeline in the Designer, then click the "Validate Pipeline" icon (usually a "V" within a cog) in the upper right corner; this will run checks on the pipeline for errors, and to execute, simply click the "Run" button or use the "Pipeline Execute" snap to trigger the pipeline execution within a larger workflow.

What is a Task in SnapLogic?

You can invoke a Pipeline execution through in the SnapLogic Platform. Tasks are how Pipelines become operational. You have access to a variety of different task types in SnapLogic and they are:

: Choose this option if you need to accomplish a job at a certain time, an interval, or a more complex schedule.
: Choose this option to enable triggering the Pipeline execution through an HTTP call. A Triggered Task can be used to build an endpoint of a web API. A Triggered Task also allows passing data into and retrieving data from a Pipeline.
: Choose this option for either specialized, low-latency jobs that need to or for Pipelines based on the . For the former, a FeedMaster node is required in the Snaplex to queue the incoming messages. The URL method is similar to Triggered Tasks, but the Pipeline design limits the usage of certain Snaps. For the latter, the Pipeline can continuously poll the target messaging service, making the Ultra Task preferable to a Scheduled Task.

Monitoring your Pipelines, Tasks and Snaps

You can track the integration's (pipeline's) performance through the Enate integration service monitoring tools.

This is available in the 'Dashboard' tab in the SnapLogic screen. You will be able to see a variety of data including the health of your pipeline as well as how it is executing Tasks. You will also be able to check your Task's health, Snaplex and APIs. For further information on reading the Dashboard in .

Alerts and how to set them up

in SnapLogic are a crucial feature designed to inform administrators and users about significant events, threshold violations, and system states within the SnapLogic integration platform. These help ensure smooth operations and timely responses to various situations.

Types of Alerts:

System-defined alerts: Automatically triggered based on predefined event parameters.
User-defined alerts: Configurable by Org admins for specific events.

Alert Categories:

Congestion Alerts: Notify when pipelines are queued for too long, indicating capacity issues.
Alert and Activity Log Notifications: Inform about events like pipeline execution exceeding usual limits.
User Notifications: Custom messages targeted to specific users.
Snaplex Notifications: Alerts for Snaplex events such as maintenance or upgrades.
Task Notifications: Inform about task execution occurrences.

SnapGPT

is SnapLogic's own built in AI assistant that can be used by all users to help answer questions, configure snaps, analyze pipelines or even generate a pipeline from scratch.

For more information, check out the dedicated article:

Using SnapGPT to help you in SnapLogic

Build your Pipeline - Enate Integration Pattern 1

Prerequisites

What you'll need in order to connect Enate with 3rd party systems using Enate Integration Services:

Enate Access – An Enate instance where you have Builder-level admin access
Enate Integration Services (Snaplogic) Access –
Familiarization with Snaplogic – see the for this.
A 3rd Party system (in this example HubSpot), where you have configuration-level admin access.

Process Overview

In Enate: External API Call – a ‘Trigger External API’ action is placed into the Case flow in Builder. This calls out to Enate Integration Services (Snaplogic) to run a specific Pipeline. Then the SnapLogic pipeline...
Calls the 3rd party System (HubSpot) – In Snaplogic a pipeline is called, this will make a call out to the 3rd party system, in this case HubSpot.
Obtains Data from HubSpot - The incoming information passed into HubSpot will allow the relevant values to be identified and sent back to Snaplogic.
Generates a Bearer Token for Accessing Enate - while this part isn't strictly necessary to complete the final snap in the pipeline (which will actually use a Callback URL for authorization instead in this example), knowing how to generate a Bearer Token for getting authorized access to your Enate system will be essential for your pipeline work going forward.
Updates Enate Data Fields & Confirms Completion of Enate Action – The updated field values are sent back to the Action in Enate, ‘Trigger External API’ action in Enate is marked as complete, allowing the Enate Case to move onto the next part of the Enate flow.

Configuration in Enate

Create Case, Custom Fields, Custom Card

Steps for the required Enate configuration are as follows:

In your Builder environment, create a new Case process for New Deals.
In conjunction, create a series of new Custom Data fields and a Custom Card for them to show on.

Set Field values as follows:

Link the Custom Card to the Case configuration.
Add a new Action at the relevant point in your Case process. You may need to create a brand new Action. Give it a sensible name, and choose type ‘Trigger External API Action’.
You’ll need to set the following information as part of the detailed Action settings:

Setting the API Integration URL & Bearer Token in your Enate API Action

https://[snaplogic pipeline link] + ‘?bearer_token=’ + [the pipeline’s bearer token’], e.g.

Check out this section on .

Additional Action Level Configuration to complete

Set an Allocation rule to route the Action back to the work item starter – this would be used in the situation where the action times out, to provide a ‘human in the loop’ to deal with any issues.

Snaplogic Pipeline Construction

Now that your Enate action to trigger your Enate Integration Services pipeline is almost complete, we can move over to Snaplogic and start to create the Pipeline. As a prerequisite, check out the section to make sure you are comfortable navigating around Snaplogic and creating Pipelines.

Pipeline Overview

Here is downloadable example of this Pipeline:

14KB

Example Pipeline_2025_02_05.slp

Walk-through of each Snap

This section walks through how to configure each of the snaps in the pipeline. Once this is done, you can . Snaps 2 & 3 relate to the third party system, in this example Hubspot. When building your own version of this, the details of how to configure equivalent snaps will obviously be specific to YOUR third party system.

Create Pipeline & Add Snap 1 - JSON Parser

Snap 2 - HubSpot Bulk Read (Accessing your 3rd Party System)

Snap 3 - HTTP Client - Get Open Deals from HubSpot (3rd Party System)

Snap 4 - HTTP Client - Get Enate Bearer Token

Snap 5 - HTTP Client - Update Action & Complete

{
  "DataFields": {
    "DealName": $original.entity.deals[0].deal_name,
    "DealType": $original.entity.deals[0].deal_type,
    "Priority": $original.entity.deals[0].priority,
    "DealAmount": $original.entity.deals[0].deal_amount,
    "DealOwner": $original.entity.deals[0].deal_owner,
   "CreatedDate": $original.entity.deals[0].created_date,
   "CloseDate": $original.entity.deals[0].close_date
  },
 "Success": true
}

How do I get Enate to call the SnapLogic Pipeline?

Create a Triggered Task & add url into Enate Action Config

To tell Enate how to call this pipeline we need to:

create a Triggered Task in SnapLogic
Paste the url for this Triggered Task back into the configuration settings for the Enate Action, along with an additional variable for a SnapLogic Bearer Token.