The systems the platform is intended to connect
The target architecture covers content publication, advertising networks, bots and conversations, CRM feedback, web events and analytics. The first commercial scope prioritises verified journeys for the initial market; the actual depth of each capability will depend on a completed pilot and the provider’s current rules.
A connection is valuable for more than the ability to send a command. It must carry stable identifiers, states and event time so that an advertisement can be related to an enquiry and the enquiry to a later outcome. Without a shared data vocabulary, automation remains a collection of isolated instructions.
What a connection means
The user sees the requested scope and the project to which the connection belongs. Credentials remain server-side. The system checks expiry, processes repeated events safely and exposes a clear state when a provider is unavailable or permission has been withdrawn.
Honest degradation
If a channel can be analysed but cannot be changed through an official programmatic interface, SintaSix should restrict itself to analysis and guidance. An integration that has not passed a live verification is not described as operational. That honesty is more valuable than a decorative wall of logos.
During a temporary failure, the platform should preserve the job context, bound its retries and explain what did not change. The user must not be left guessing whether a publication was duplicated or whether budget was spent during another attempt.
A connection can be withdrawn
External access is never assumed to be permanent. An owner should be able to inspect its state and revoke it. New actions stop after revocation, while historical records preserve provenance and explain why further updates are unavailable.