Skip to main content
Use the @bijection/connectors/act-on entrypoint to declare Act-On resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Contact list

pull: Whole list export by anchored download pages

The following example matches configuration standard.

Configuration: standard

Case: act-on/contacts/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: acton. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: contacts
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Suppression lists

pull: Suppression entries from a carried createdafter

The following example matches configuration standard.

Configuration: standard

Case: act-on/suppressions/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: acton. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: suppressions
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection’s host is api.actonsoftware.com (or api-eu.actonsoftware.com). The acton credential is an OAuth grant from Act-On’s password or authorization-code flow, renewed by its refresh token; Act-On allows five password or code exchanges an hour, and documents no client-credentials grant. No account identity is documented. The budget is five calls a second; the 30,000-a-day limit has no documented reset and is not declared. Act-On has no export job; a list is exported by paging its download. contacts.pull reads one contact list each pass with an anchored offset walk over GET /api/1/list/<id> (JSON, 100 rows). Each row is keyed by _contact_id_; the list’s columns are published as JSON text of header to value, beside the email column. The walk is whole because no static selector names a row’s modification date (datequalifiers places the date columns per list), so modafter cannot be carried with a version. Removed contacts stay published. suppressions.pull reads a system list (hardbounce, spamcomplaint, optout): each entry is keyed by address and timestamp (milliseconds) and never changes. A finished pass carries the provider Date of its first page; the next filters createdafter ten minutes before it, in seconds, because the unit is undocumented and seconds read as milliseconds would select every entry rather than none. Removed suppressions stay published. Nothing here has run against Act-On.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.