Appearance
Constant Contact Connection
The Constant Contact Connection authorizes supported Constant Contact operations for contacts, contact lists, email campaigns, and campaign reporting.
Use it from Cloud Flow through Connection methods or the $io.constantContact Server API. It is not exposed as a general Connection command in the Page Flow or Cloud Flow command selector.
Capabilities
| Capability | Availability |
|---|---|
| Connection service identifier | constantcontact |
| Page Flow commands | Not exposed |
| Cloud Flow direct commands | Not exposed in the command selector |
| Connection methods | Supported |
| Server API | $io.constantContact |
| Connection-backed SDK object | Not documented |
| AI Agent Connection support | Supported |
Authentication Modes
The Profile supports:
| Mode | Use |
|---|---|
| OAuth2 | Authorize through the ioLoop-provided Constant Contact OAuth application. |
| Custom OAuth2 | Authorize through your own Constant Contact application. |
Custom OAuth2 uses a client ID, client secret, and optional space-separated scopes. Configure the provider application's redirect URL and authorization settings before creating the Profile.
The Connection has no additional service settings beyond its name and selected Profile.
Server Methods
The Constant Contact Server API includes supported operations for:
- Listing, retrieving, creating, updating, and searching contacts.
- Listing contact lists and retrieving contacts in a list.
- Adding contacts to or removing contacts from a list.
- Listing and retrieving campaigns.
- Retrieving campaign statistics, clicks, and bounces.
- Following supported pagination links.
- Executing a supported authenticated API request.
Use the Connection Function Call block or $io.constantContact for exact method signatures and return values.
Security and Workflow Design
Keep contact and campaign changes in trusted Cloud Flow. When a Page submits contact information, validate consent, required fields, list selection, and caller permissions before invoking the Connection.
Do not expose a generic provider path-and-method interface to untrusted browser input. Prefer named methods that represent the allowed business operation.
Testing
Use controlled contacts, lists, and campaigns. Confirm that the OAuth Profile has the required scopes and that the selected account is appropriate for development.
Test pagination, duplicate contacts, invalid addresses, missing scopes, and provider rate limits. Cloud Flow tests can change real marketing data or contact membership.