← Back to connectors

Battle.net connector for Okou

Connect Battle.net to read your Battle.net identity and World of Warcraft profile data through fixed US API endpoints.

Data & infrastructure · OAuth (Recommended)

Use Battle.net in Okou

Battle.net identity and World of Warcraft profile access through the official OAuth APIs.

Once connected, supported Battle.net 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 Battle.net

  • Read the connected Battle.net identity and authorized World of Warcraft profile data.

How the Battle.net connector works

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

  1. 1

    Connect Battle.net

    Choose OAuth (Recommended).

  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 Battle.net securely

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

  • OAuth (Recommended)

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.

Battle.net connector questions

What can Okou do with Battle.net?
Connect Battle.net to read your Battle.net identity and World of Warcraft profile data through fixed US API endpoints. Documented actions include: Read the connected Battle.net identity and authorized World of Warcraft profile data.
How do I connect Battle.net to Okou?
Connect Battle.net using OAuth (Recommended). The connection controls which supported actions a workflow can use.
Can Battle.net run in an automated workflow?
Yes. After it is connected, supported Battle.net actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.

More data & infrastructure connectors

Explore other connectors in the same product category.