Apps connect Omni Impact to your publishing platforms and knowledge sources. Use the Browse tab to connect an app and Connected to manage existing connections.
Choose a connection
Choose the app for your destination, then check its publishing support before making a change. Support varies by provider, permissions, and site configuration.
| App | Connection and actions | Publishing guidance |
|---|---|---|
| WordPress (Self-Hosted) | Create and update posts and pages. | Follow the WordPress setup guide. |
| GitHub App | Publish reviewed file changes to a selected repository. | Follow the GitHub setup guide. |
| WordPress.com | Hosted WordPress connection. | Confirm support for your site before publishing. |
| Wix, Webflow, Contentful, Notion, HubSpot, DatoCMS, Duda | Content-platform connections. | Publishing support and required fields vary. Confirm your destination with support. |
| Atlassian, Linear, Dropbox | Knowledge connections. | Use these as knowledge sources; no content-publishing setup is provided here. |
For publishing setup, start with WordPress (self-hosted). Google Analytics has a separate read-only analytics connection.
Connect and check an app
To connect an app, follow its authorization flow or enter the credentials requested by its form.
- Open Browse in Apps.
- Select Connect or Install for your app.
- Approve the requested access, or provide the fields shown in the connection form.
- Open Connected and check the connection status.
- Use the connection test when you need to check access again.
Healthy means the last connection test succeeded. Reauth needed asks you to reconnect. Failed means the test failed; inspect the message and check the provider's permissions or availability before trying again.
In an organization, select the client workspace you want to work in before connecting or publishing. Portfolio view disables these actions. Some providers also require a site-specific selection; contact support if a connected app refuses a client-workspace action.
Understand the write boundaries
Revert is available for eligible self-hosted WordPress updates with a saved previous body and for successful GitHub App changes. Other connections do not have the same one-click revert capability.
The overwrite warning for self-hosted WordPress updates cannot detect every conflict. An update may still proceed when the live page cannot be checked. Review the WordPress limitations before replacing content.
The Omni agent asks for your confirmation before publishing to an app. Review the destination and proposed content when you approve.
How credentials are stored
App credentials are stored encrypted. Keep passwords and tokens out of support messages.
Use the Connected tab to reconnect or disconnect an app.