AETERION

    HubSpot

    HubSpot integration

    CRMAvailable

    BRAIAN connects to HubSpot through Private app token. Agents can contact and deal read, lifecycle stage updates and campaign data read. Every action is scoped by the permissions granted to the integration and executed under a versioned policy. Each one is recorded in the audit log with the agent, timestamp and record touched.

    What can BRAIAN do?

    SalesAgent and MaAgent read contacts, deals and campaign data, update lifecycle stages and log the activities they perform. The connection uses a private app token whose scopes are set per portal.

    CapabilityAgentRead or write
    Contact and deal readSalesAgentRead
    Lifecycle stage updatesMaAgentWrite
    Campaign data readMaAgentRead
    Activity loggingSalesAgentWrite

    How does it connect?

    Connection method
    Private app token
    Credential
    A HubSpot private app token, created in the customer portal and revocable there at any time.

    Credentials are held in an encrypted secrets store. BRAIAN never stores end-user passwords.

    Which permissions are required?

    • crm.objects.contacts / crm.objects.dealsRead and write on the CRM objects the configured processes use.
    • marketing.campaigns.readCampaign performance data, read only.

    Permissions are requested at the minimum scope the configured processes require. Unused scopes are not granted.

    Which processes use it?

    Processes that run on this connection, and the domains they belong to.

    • Inbound process

    • Outbound process

    • Offering

    How do you revoke access?

    Access is revoked in HubSpot itself — by disabling the credential or removing the granted scopes — or in BRAIAN by disconnecting the integration. Processes already running stop at their next call to HubSpot and are held for review rather than completed with partial data; the interruption and the state of each process are recorded in the audit log.

    FAQ

    Does BRAIAN store data from HubSpot?

    BRAIAN reads what a process needs, when it needs it. Records retrieved from HubSpot are held only for the duration of the process and in the audit trail of the actions taken; HubSpot remains the system of record.

    What happens if the connection fails mid-process?

    The process stops at the failed step and is held for review. Nothing is written twice: completed writes stay recorded in the audit log and the remaining steps resume only once the connection is restored.

    Can permissions be scoped per agent?

    Yes. Scopes are defined per agent, not per system, so one agent can read while another cannot, on the same connection to HubSpot.