Integrations

Six channels, each a direct integration with the platform’s own API.

No middleman holds your tokens and no third-party scheduler sits in the path. Every page below states the permissions Opal asks for, in the platform’s own scope names, and what it does with each one.

Live today

The channels.

Connecting

How a connection is made, and unmade.

The same four steps on every platform.

  1. 01

    You start from Channels

    Inside Opal, on the brand whose account you are connecting. Nothing happens on the platform until you do this.

  2. 02

    The platform asks, not us

    You land on the platform’s own sign-in and consent screen, which lists the permissions being requested. Opal never sees or asks for your platform password.

  3. 03

    The token comes back encrypted

    Opal stores the access token encrypted at rest and decrypts it only at the moment of a call. Alongside it, it stores the account name and avatar so you can see which account is connected.

  4. 04

    You can end it whenever you want

    Disconnect inside Opal to delete the token, or revoke from the platform’s own app-permissions screen. Either one stops publishing immediately.

Not yet

Channels that are built but not open.

YouTube

Video publishing waits on the media pipeline.

Dribbble

Shot publishing is built and off by default.

We list these because a channel being present in the code is not the same as a channel you can connect. When one opens, it opens on this page first.

See it on your brands.

A 30-minute call: your channels, your calendar, and what Opal would take off your plate first.