Loading workspace...
Auroranexis documentation
Integrations connect Auroranexis to the CRM, ticketing, messaging, and productivity systems your agency already uses. Authorize connectors via OAuth at Automation → Connectors, run sync where supported, store API keys at Integrations → Secrets, and diagnose delivery through integration logs. Connectivity established here powers automation workflows and keeps operational data aligned with external tools your delivery, sales, and support teams monitor daily.
The integration catalog lives under Automation in the dashboard. Each connector represents a supported external platform—CRM tools like HubSpot and Salesforce, ticketing systems like Jira, Linear, and Zendesk, messaging via Slack and Microsoft Teams, and workspace productivity through Google and Microsoft 365.
Connections are organization-scoped. An admin or authorized integration owner completes the OAuth flow once per connector per workspace. Connected systems become available to automation workflows and, where supported, scheduled sync jobs that keep selected records aligned even when no platform trigger fires.
Integration activity—successful deliveries, sync runs, OAuth refreshes, and errors—is recorded in integration logs for operational visibility. Logs are the first place to look when CRM data is stale, tickets fail to create, or channel messages stop arriving.
Agencies operate across many tools. Auroranexis is the operational source of truth for client health, incidents, and reports; integrations extend that truth into systems your delivery, sales, and support teams already monitor.
Without integrations, operators manually copy incident summaries into ticketing systems, log delivery milestones in CRMs, and post status updates in chat channels. Connectors and sync reduce that friction while preserving Auroranexis as the authoritative record for SLA compliance and client reporting.
Contact support@auroranexis.com for onboarding support, billing questions, or product guidance. Include your workspace name, the module you are working in, and a brief description of your goal so we can respond efficiently.
Integrations establish connectivity and optional sync. Automation consumes that connectivity in workflows. Connect first at Automation → Connectors; then reference connectors in workflow actions. Manage API keys at Integrations → Secrets when OAuth alone is insufficient for a given endpoint or custom integration.
Connector categories (representative)
| Category | Examples | Typical use |
|---|---|---|
| CRM | HubSpot, Salesforce | Log activities, update deals or opportunities |
| Helpdesk / ticketing | Zendesk, Jira, Linear | Create or update tickets from incidents |
| Messaging | Slack, Microsoft Teams | Channel alerts for operational events |
| Workspace | Google, Microsoft 365 | Email, calendar, and document workflows |
| DevOps | GitHub, GitLab | Link incidents to issues and pipelines |
A connector is a pre-built integration module for a specific external platform. Each connector declares supported actions (write operations), inbound triggers where applicable, and OAuth requirements. Browse the full catalog at Automation → Connectors.
A performance marketing firm connects HubSpot and Slack at Automation → Connectors. A workflow logs HubSpot activities when reports publish; Slack receives channel alerts for client health drops. Weekly sync keeps deal stages aligned with client status changes in Auroranexis. Integration logs confirm each sync run; the ops lead reviews failures every Monday.
An AI consultancy connects Linear, GitHub, and a custom webhook via Integrations → Secrets. Incident workflows create Linear issues linked to GitHub repositories mentioned in incident notes. The webhook posts structured payloads to an internal orchestration layer. OAuth covers Linear and GitHub; the webhook secret rotates quarterly.
An MSP connects Zendesk and Microsoft Teams for NOC operations. High-severity incidents create Zendesk tickets automatically; Teams channels receive bridge-call summaries. Sync pulls ticket status back for display on incident detail pages where supported. Integration logs filter quickly to Zendesk when clients report missing tickets.
A management consultancy connects Salesforce only for strategic accounts. Workflows log delivery milestones when reports publish; sync is limited to opportunity stages for those clients. Messaging integrations are intentionally omitted to keep client communication human-led. Logs are reviewed monthly because write volume is low.
An enterprise agency authorizes connectors through a dedicated integration service account at each provider. Salesforce, Jira, and Teams are connected once per workspace with secrets stored in a managed rotation process. Sync jobs run on conservative schedules to respect enterprise API quotas. Integration logs export to the compliance team quarterly.
Integration troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| OAuth authorization fails | Insufficient permissions at the provider or conflicting browser session. | Sign in with an admin or integration-manager account; try an incognito session; verify redirect URLs for your deployment. |
| Connector shows error status | Expired token or revoked application consent. | Click Reconnect at Automation → Connectors; verify the app was not removed in the provider's connected-apps settings. |
| Sync delayed or incomplete | API rate limits or reduced scope on the connected account. | Review integration logs for the latest sync run; narrow sync scope or increase interval; confirm account access to synced resources. |
| Workflow action fails despite connected status | OAuth token lacks a required scope. | Disconnect and reconnect granting full requested permissions; check Integrations → Secrets if the action uses a stored API key. |
Most connectors use OAuth 2.0. An authorized user is redirected to the external provider, grants consent, and is returned to Auroranexis with a stored refresh token. The platform uses that token for subsequent API calls on behalf of your organization until consent is revoked or the token expires.
Each connector shows connected, disconnected, or error state on the Connectors page. Error state usually indicates an expired token, revoked consent, or misconfigured environment credentials. Click Reconnect to repeat the OAuth flow.
Supported connectors can run sync jobs that pull or push selected data on a schedule or on demand. Sync complements event-driven automation for data that must stay current even when no platform trigger fires. Sync runs appear in integration logs with record counts and error summaries.
Every significant integration operation—OAuth refresh, sync run, workflow action delivery—is logged with timestamp, connector, outcome, and error detail when applicable. Open Automation → Integrations → Logs to review recent activity across all connectors.
Some custom or legacy endpoints require API keys stored at Automation → Integrations → Secrets. Secrets are encrypted at rest, referenced by connector configuration or workflow actions, and should be rotated on your security schedule.
| Duplicate records in external system | Multiple workflows or connections writing the same data. | Consolidate workflows; maintain one canonical connector; add conditions to prevent repeat writes. |
| Connector not listed in catalog | Plan does not include the integration or environment configuration is incomplete. | Review Settings → Billing; contact support if the catalog is unexpectedly empty for your tier. |
| Integration logs show repeated OAuth refresh failures | Provider policy change or revoked refresh token. | Reconnect the connector; confirm the authorizing user account is still active at the provider. |
