foxora

Channels

Channels bring Fennec into messaging, email, event, and voice services while Foxora hosts the connection runtime. Each installation combines provider credentials, a compatible crew, and channel-specific access rules.

In this section 6 pages

  1. 25.01Channels overview
  2. 25.02Connecting a channelConnectors use either provider sign-in or credentials defined by that provider. Foxora then asks how Fennec should answer and, when required, shows provider-side webhook details.
  3. 25.03Routing channel messagesChannels route messages through a crew selected as the channel's Fennec mode; they do not assign an individual agent or a separate bot record directly.
  4. 25.04Channel permissionsChannel permissions narrow what Fennec may do when a message comes from an external audience. They supplement verified sender identity and runtime authorization; free-form guidance is not a security boundary.
  5. 25.05Managing connected channelsUse the Channels list to inspect an installation, update safe settings without re-entering unchanged secrets, or remove a provider route you no longer use.
  6. 25.06Channel troubleshootingA connected badge proves saved configuration, not the full provider-to-Foxora message path. Diagnose the row status, provider callback, identity verification, and a real event in that order.