Version: 17.07
Supported Since: 17.07
Act-On egress connector can be used to communicate with Act-On APIs for information retrieval and update operations on entities such as Lists, Email Campaigns, Contacts, etc.
This connector also handles OAuth operations related to the Act-On API such as retrieving and caching the authentication token, attaching the token to API requests and refreshing the token on expiration.
By default, this connector will fetch the list of all Lists in a given Act-On Account. This behaviour can be changed by using this in combination with one of its available connector operations.
In order to use the Act-On Egress Connector, you must first select the Act-On Connector dependency from the connector list when you are creating an empty Ultra project. If you have already created a project, you can add the Act-On Connector dependency via Component Registry. From Tools menu, select Ultra Studio → Component Registry and from the Connectors list, select the Act-On Connector dependency. |
On Exception |
The message will be emitted from this out port if the connector failed to send the message to the intended Act-On endpoint. |
Response Processor |
The response message received from Act-On will be directed to this port. You can use this port to connect any precessing element or connector that is supposed to process/consume the response. |
Connector Operation |
This port is used to connect operational elements to the Egress Connector |
* marked fields are mandatory
Username * |
Basic |
The email address of a user in the Act-On account you are trying to access |
Password * |
Basic |
The password associated with the username |
Client ID * |
Basic |
Client ID of API developer to be used to connect to Act-On API. Usually, when you register in Act-On, you will receive a Client ID for your sandbox account via email. |
Client Secret * |
Basic |
Client Secret of API developer to be used to connect to Act-On API |
API Version |
Basic |
Version of the Act-On APIs to be used. The default value is |
Egress Timeout |
Advanced |
Timeout in milliseconds after which the egress message times out |