← Back to connectors

Twake connector for Okou

Connect Twake to send and remove application messages in Twake channels through its documented developer API.

Communication · Application ID and Private API Key

Use Twake in Okou

Use Twake's documented developer API to send or remove application messages.

Once connected, supported Twake actions can become steps in a reusable workflow alongside the other services your team uses. Run the workflow once, on a schedule, or when an event starts it.

What you can do with Twake

  • Send an application message to a Twake channel; this changes provider state and requires the Twake message_save privilege.

How the Twake connector works

A connected service becomes one permissioned step in the work you hand off.

  1. 1

    Connect Twake

    Choose Application ID and Private API Key.

  2. 2

    Choose the work

    Use only the supported actions your workflow needs.

  3. 3

    Run it your way

    Start it once, schedule it, or attach an event trigger.

Connect Twake securely

Use the connection method that fits your account and grant only the access the workflow needs.

  • Application ID and Private API Key

Connector access is controlled per service and per action, so a workflow does not need broader access than the work you ask it to do.

Twake connector questions

What can Okou do with Twake?
Connect Twake to send and remove application messages in Twake channels through its documented developer API. Documented actions include: Send an application message to a Twake channel; this changes provider state and requires the Twake message_save privilege.
How do I connect Twake to Okou?
Connect Twake using Application ID and Private API Key. The connection controls which supported actions a workflow can use.
Can Twake run in an automated workflow?
Yes. After it is connected, supported Twake actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.

More communication connectors

Explore other connectors in the same product category.