Supported objects and operations
The ActiveCampaign connector allows you to connect ActiveCampaign with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance ActiveCampaign’s wide range of marketing services and solutions.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Users
Table 306: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User |
GET |
Get All users |
GET |
Groups
Table 307: Supported operations for Groups
Create Group |
POST |
Update Group |
PUT |
Get Group |
GET |
Delete Group |
DELETE |
Get Group Members |
GET |
Get all Groups |
GET |
Mandatory fields
This section lists the mandatory fields required to create Users and Groups.
Users
-
Name.GivenName
-
Name.FamilyName
-
Email
-
Username
-
password
-
GroupId
Groups
DisplayName
User and Group mapping
The user and group mappings are listed in the tables below.
Users
Table 308: User mapping
Id |
id |
UserName |
username |
DisplayName |
firstName+ lastName |
Name.GivenName |
firstName |
Name.FamilyName |
lastName |
Emails.Value |
email |
Groups[].value (readOnly) |
groupid |
PhoneNumbers[].value |
phone |
Meta.Created |
cdate |
Meta.LastModified |
udate |
Password |
Password |
userExtension.groupId (WriteOnly) |
groupid |
Table 309: Group mapping
Id |
Id |
displayName |
title |
members[].value |
(groupMembersResponse) userid |
groupExtension.Description |
Descript |
Connector limitations
-
GroupId is a writeOnly mandatory extension property while creating or updating a User.
-
Membership operations are not implemented due to the unavailability of APIs.
-
The Groups property in the schema of the User is an on-demand attribute, which will not be fetched during the operation GET User by Id unless the request has an attribute for groups.
Mandatory fields
The ActiveCampaign connector allows you to connect ActiveCampaign with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance ActiveCampaign’s wide range of marketing services and solutions.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 306: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User |
GET |
Get All users |
GET |
Groups
Table 307: Supported operations for Groups
Create Group |
POST |
Update Group |
PUT |
Get Group |
GET |
Delete Group |
DELETE |
Get Group Members |
GET |
Get all Groups |
GET |
This section lists the mandatory fields required to create Users and Groups.
Users
-
Name.GivenName
-
Name.FamilyName
-
Email
-
Username
-
password
-
GroupId
Groups
DisplayName
User and Group mapping
The user and group mappings are listed in the tables below.
Users
Table 308: User mapping
Id |
id |
UserName |
username |
DisplayName |
firstName+ lastName |
Name.GivenName |
firstName |
Name.FamilyName |
lastName |
Emails.Value |
email |
Groups[].value (readOnly) |
groupid |
PhoneNumbers[].value |
phone |
Meta.Created |
cdate |
Meta.LastModified |
udate |
Password |
Password |
userExtension.groupId (WriteOnly) |
groupid |
Table 309: Group mapping
Id |
Id |
displayName |
title |
members[].value |
(groupMembersResponse) userid |
groupExtension.Description |
Descript |
Connector limitations
-
GroupId is a writeOnly mandatory extension property while creating or updating a User.
-
Membership operations are not implemented due to the unavailability of APIs.
-
The Groups property in the schema of the User is an on-demand attribute, which will not be fetched during the operation GET User by Id unless the request has an attribute for groups.
User and Group mapping
The ActiveCampaign connector allows you to connect ActiveCampaign with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance ActiveCampaign’s wide range of marketing services and solutions.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 306: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User |
GET |
Get All users |
GET |
Groups
Table 307: Supported operations for Groups
Create Group |
POST |
Update Group |
PUT |
Get Group |
GET |
Delete Group |
DELETE |
Get Group Members |
GET |
Get all Groups |
GET |
Mandatory fields
This section lists the mandatory fields required to create Users and Groups.
Users
-
Name.GivenName
-
Name.FamilyName
-
Email
-
Username
-
password
-
GroupId
Groups
DisplayName
The user and group mappings are listed in the tables below.
Users
Table 308: User mapping
Id |
id |
UserName |
username |
DisplayName |
firstName+ lastName |
Name.GivenName |
firstName |
Name.FamilyName |
lastName |
Emails.Value |
email |
Groups[].value (readOnly) |
groupid |
PhoneNumbers[].value |
phone |
Meta.Created |
cdate |
Meta.LastModified |
udate |
Password |
Password |
userExtension.groupId (WriteOnly) |
groupid |
Table 309: Group mapping
Id |
Id |
displayName |
title |
members[].value |
(groupMembersResponse) userid |
groupExtension.Description |
Descript |
Connector limitations
-
GroupId is a writeOnly mandatory extension property while creating or updating a User.
-
Membership operations are not implemented due to the unavailability of APIs.
-
The Groups property in the schema of the User is an on-demand attribute, which will not be fetched during the operation GET User by Id unless the request has an attribute for groups.
Connector limitations
The ActiveCampaign connector allows you to connect ActiveCampaign with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance ActiveCampaign’s wide range of marketing services and solutions.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 306: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User |
GET |
Get All users |
GET |
Groups
Table 307: Supported operations for Groups
Create Group |
POST |
Update Group |
PUT |
Get Group |
GET |
Delete Group |
DELETE |
Get Group Members |
GET |
Get all Groups |
GET |
Mandatory fields
This section lists the mandatory fields required to create Users and Groups.
Users
-
Name.GivenName
-
Name.FamilyName
-
Email
-
Username
-
password
-
GroupId
Groups
DisplayName
User and Group mapping
The user and group mappings are listed in the tables below.
Users
Table 308: User mapping
Id |
id |
UserName |
username |
DisplayName |
firstName+ lastName |
Name.GivenName |
firstName |
Name.FamilyName |
lastName |
Emails.Value |
email |
Groups[].value (readOnly) |
groupid |
PhoneNumbers[].value |
phone |
Meta.Created |
cdate |
Meta.LastModified |
udate |
Password |
Password |
userExtension.groupId (WriteOnly) |
groupid |
Table 309: Group mapping
Id |
Id |
displayName |
title |
members[].value |
(groupMembersResponse) userid |
groupExtension.Description |
Descript |
-
GroupId is a writeOnly mandatory extension property while creating or updating a User.
-
Membership operations are not implemented due to the unavailability of APIs.
-
The Groups property in the schema of the User is an on-demand attribute, which will not be fetched during the operation GET User by Id unless the request has an attribute for groups.