This article describes how to set up the Agillic Recipients connector.
Table of Contents Placeholder
Connector Actions
Action Name |
AudienceStream |
EventStream |
Add or Update Recipient |
✓ |
✓ |
Update Recipient Table Records |
✓ |
✓ |
Achieve Event |
✓ |
✓ |
Configure Settings
Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.
After adding the connector, configure the following settings:
- Client ID
- Client Secret
- Required.
- Provide your web application client secret.
- Date Format
- Set the date format for the connector.
- If not specified, the default format
dd.MM.yyyy
is used.
- The date and timestamp format is unique to each Agillic account instance.
- Formats are defined in the Agillic Administration interface.
- For more information, see Getting Started with APIs: Dates and Time.
- Timestamp Format
- Set the timestamp format for the connector.
- If not specified, the default format
dd.MM.yyyy
is used.
Action Settings - Parameters and Options
Click Next or go to the Actions tab. This is where you configure connector actions.
This section describes how to set up parameters and options for each action.
Action - Add or Update Recipient
Parameters
Parameter |
Description |
Recipient ID |
- Required.
- Map any unique Person Data, such as EMAIL or MOBILE.
- Use Recipient ID for general purpose.
- For more information, see APIs: Recipient API.
|
Recipient Data |
- Required.
- Map values to the Person Data fields.
|
Action - Update Recipient Table Records
Parameters
Parameter |
Description |
Recipient ID |
- Required.
- Map any unique Person Data, such as EMAIL or MOBILE.
- Use Recipient ID for general purpose.
- For more information, see APIs: Recipient API.
|
Table |
- Required.
- Table ID of the records that will be batch updated.
|
Table Record |
- Required.
- Map one or more values to each table record field.
- ID or Primary Key must be specified.
|
Action - Achieve Event
Parameters
Parameter |
Description |
Recipient ID |
- Required.
- Map any unique Person Data, such as EMAIL or MOBILE.
- Use Recipient ID for general purpose.
- For more information, see APIs: Recipient API.
|
Event ID |
- Required.
- Event ID to be achieved.
|