Integrations overview
Connect sources and destinations with the least access the workflow needs.
Choose the job first
Integrations have different jobs: importing company knowledge, reading analytics, publishing content, proposing code changes or routing conversation. Connect a service because you need that job, not because it appears in the catalogue.
The following guides are drawn from Obelo’s in-app setup instructions. Availability still depends on the current deployment, plan, provider approval and your permissions. A guide documents a setup path; the runtime status determines whether you can complete it today.
The connection lifecycle
- Open Settings → Integrations and choose a provider.
- Read its prerequisites and whether setup is Obelo-managed or customer-managed.
- Complete the provider’s authorization or enter the required dedicated credential in the application’s secure form.
- Select the exact resource: site, collection, property, repository, channel or account.
- Run verification or a read-only sync and inspect its result.
- For publishing, approve a real output and verify its destination before delivery.
Interpret connection states
Connected means authorization exists; it does not necessarily mean the source has synchronized or a publication succeeded. “No resources” can mean insufficient provider permissions or that the required property has not been created. “Platform unavailable” requires help from Obelo, not another attempt with your password.
Disconnect safely
Disconnect in Settings to stop the local connection. Revoke the grant or rotate the dedicated credential at the provider when necessary. Disconnection is different from deleting already-imported documents, historical analytics or published posts. Use the relevant data-control workflow for those records.
Something unclear or out of date?
Suggest a correction