Two types of node can be implemented in custom integrations:
- Action nodes
- Entry point nodes
An Action Node implements an Automation Center action. When a contact progressing through an Automation Center program reaches your action node, the program will call the specified Trigger endpoint with a set of parameters, including a contact list ID. You can then use this endpoint to trigger the desired actions for the contacts entering the node.
When the Emarsys user adds the node to an Automation Center program, they also have the option to configure it. This can be done by simply selecting a resource (see Resource Options endpoint), for example a campaign, or by using a more complex configuration (see Custom Node Dialog endpoint). This information will be sent to the trigger endpoint.
An action node must implement the Trigger Endpoint, and can optionally implement a Resource Options Endpoint or Custom Node Dialog Endpoint.
Entry Point Nodes
An entry point node implements an Automation Center program entry point. Entry points are the first node of an Automation Center program, and start a contact’s progress through the program.
For example, for a specific event that occurs on your side, you call the start program API endpoint and create an entry point triggered by that event. Once the entry point is added to a program, contact interaction with the event will start their progress through the program.
If the resource is also specified, then it will be narrowed down to only the nodes configured with that resource.
The following is a requirements checklist regarding the information we need to create and enable an Automation Center node. We also have collected and included some best practices based on our experience with Emarsys integrations.
The following is a collection of resources which can help with e.g. providing the details of the contacts from the
contact list specified at the trigger endpoint, or information about the usage of a resource.