@bijection/connectors/act entrypoint to declare Act! CRM 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.
Contacts, companies and opportunities
pull: edited windows over OData query options, no deletions
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:act/records/pull/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: act. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
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. Setupendpoint is the Act! Web API base (https://<host>/act.web.api/, or the
Premium Cloud -api host). The credential is a managed session_login
envelope: the host calls GET /authorize with the user’s Basic credentials and
the Act-Database-Name header, presents the token it answers as a bearer, and
logs in again after lifetime_seconds or once on a rejected session:
lifetime_seconds is the
host’s reuse bound.
The login endpoint must be https://; a session login over a relay route to an
IIS http:// binding is refused, and logging in through a relay route is
unverified.
On premises. An Act! Web API on the customer’s IIS is reached through a
network relay: the connection’s typed setup carries
network: { relay: "<group>", target: "<name>" }, and the endpoint’s host and port
equal that relay target’s. Act!‘s own examples use http://; plain http:// is
admitted only on a relay route, where the bearer token and every record cross the
customer’s network unencrypted, so prefer an IIS HTTPS binding. A publicly
reachable server needs https://.
records.pull reads contacts, companies or opportunities with
$filter=edited ge, $orderby=edited asc,id asc, 100 rows by $skip,
re-asking from one second before the latest edited read, and carries the latest
one to the next pass. No deletion is observable and no write is declared. Nothing
here has run against Act!.
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.