Act-On - REST Api - Add Lead

A connection is established between your ion console and your Act-On instance. Next a field mapping is completed in ion to define which ion fields should be exported and how they correspond to your Act-On list fields.

Step 1

Credentials

Ask the client to setup their credentials to their console you can provide the following URL with the placeholder replaced

{console}.postclickmarketing.com/Admin/Integration/ExternalServices

Within the Custom Category the client needs to create two new entries (suggested labels Act-On User Credentials and Act-On API Credentials).

In the first entry (Act-On API Credentials) they place their clientID as username and the clientSecret as Password.

In the second entry (Act-On User Credentials) they place their username and password of the user they want to utilize for authentication.

Example: Act-On API Credentials

Example: Act-On Login Credentials

Step 2

Fieldmapping

Setup the Fieldmapping based on the Worksheet provided by the client. And adjust the demo form in their console to match all the fields they want to collect.

Example: Act-on - REST API - fieldmapping

As this is a POST XML/JSON integtration also the JSON part will need to be adjusted for every field added.

Note: The access_token is not mapped directly in the JSON but is a dynamic variable in the integration settings. However it is added to the fieldmapping to prevent submissions if it is missing.

Example: Act-on - REST API - settings

Recommendation: In order to keep Fieldmappings as flexible as possible only make the e-mail address required. This tends to allow the fieldmapping to be reused with a lot of variations of form in creative.

In order to dispel the concerns of the client. Fields can still be made required in the form in the creative to make sure all data they want is collected.

Step 3

Integration

Setup the Integration using the Fieldmapping created in the previous step.

Ensure the Method for this call is set to PUT
Add the HTTP content type as application/json
Add the additional HTTP Header
- Using Authorization as name
- Using Bearer {{access_token}} as value

Example: Act-on - REST API - Add Lead

Step 4

Server Scriptlet

Create a new Server scriptlet in their console.

You should be able to directly copy the code from the Server Scriptlet Example.

Depending on the names chosen for the credentials and the integrations itself the lines 2,3 and 4 might need to be updated to match the chosen names.

Example: Act-On - Auth/RunIntegration

When triggered the scriptlet is running a request to the authentication endpoing for Act-on using the clientID and clientSecret from Zoho CRM API Credentials as well as the username and password from Act-On User Credentials.

And then triggers the integration named on line 4 e.g.: Act-on - Rest API - Add Lead

Step 5

Creative

Add the trigger for the Server Scriptlet. This is usually the submit button on the form. But can be placed anywhere that allows you to add Rules to an action or a Page.

Example: Act-on - REST-API - Add Lead

Note: The Mark to re-run rule is integrated in the server scriptlet on line 57 (actionMarkReexport)

Form Headline Goes Here

First Name *

Last Name *

Email *