Who can authorize OAuth connectors?

Users with permission to manage automation and integrations can complete OAuth flows. Restrict this to trusted admins because connected tokens act on behalf of your entire organization.

Where are integration logs?

Open Automation → Integrations → Logs. Entries include connector name, operation type, timestamp, and success or failure detail.

Does sync replace automation?

No. Sync jobs track connector health and job metadata; v1 sync counts are simulated and do not guarantee production data replication. Automation reacts to platform events in real time. Most agencies use connectors for authorization/actions and automation for event-driven work.

How do I store an API key instead of using OAuth?

Add the key at Automation → Integrations → Secrets. Reference it from the connector or workflow configuration that requires manual credentials.

What happens if I disconnect a connector?

Workflow actions targeting that connector will fail until you reconnect or update the workflow. Disable affected workflows before disconnecting to avoid repeated failed executions.

Which connectors are available on my plan?

Connector availability depends on your subscription tier. Review the catalog at Automation → Connectors and Settings → Usage for plan-specific entitlements.

Integrations

Auroranexis documentation

All docs

Integrations connect Auroranexis to the CRM, ticketing, messaging, and productivity systems your agency already uses. Authentication method depends on the integration and may include OAuth, API credentials, webhook configuration, or manual setup. Authorize connectors 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.

Category	Examples	Typical use
Messaging	Slack, Microsoft Teams, Discord	Live outbound channel notifications when secrets are configured
Webhook	Generic webhook	Live outbound HTTPS delivery with retries
CRM (catalog)	HubSpot, Salesforce	Authorization and sync scaffolding in v1 — not live CRM writes
Helpdesk / ticketing (catalog)	Zendesk, Jira, Linear	Authorization and scaffolding in v1 — not live ticket writes
Workspace (catalog)	Google, Microsoft 365	Catalog entries for productivity tooling; treat as scaffolding unless live execution is confirmed

Problem	Cause	Solution
OAuth authorization fails	Insufficient permissions at the provider or conflicting browser session.	Sign in with an account that has permission to manage integrations; 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	Token or credentials lack a required scope.	Disconnect and reconnect granting full requested permissions; check Integrations → Secrets if the action uses a stored API key.

Integrations

Overview

Purpose

Primary use cases

FAQ

Need help?

Integration vs. automation

Core Concepts

Features

Step-by-step usage

Revoking a connection

Best Practices

Examples

Marketing agency

AI automation agency

MSP

Consultancy

Enterprise deployment

Troubleshooting

Connector

Authentication

Connection status

Sync

Integration logs

Secrets