← Back to connectors

Torq connector for Okou

Read Torq workflows, cases, executions, observables, and runbooks.

Data & infrastructure · Bearer Access Token

Use Torq in Okou

Torq REST API for reading security workflows, cases, executions, observables, and runbooks.

Once connected, supported Torq 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 Torq

  • Read Torq workflows, cases, executions, observables, and runbooks.

How the Torq connector works

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

  1. 1

    Connect Torq

    Choose Bearer Access Token.

  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 Torq securely

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

  • Bearer Access Token

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.

Torq connector questions

What can Okou do with Torq?
Read Torq workflows, cases, executions, observables, and runbooks. Documented actions include: Read Torq workflows, cases, executions, observables, and runbooks.
How do I connect Torq to Okou?
Connect Torq using Bearer Access Token. The connection controls which supported actions a workflow can use.
Can Torq run in an automated workflow?
Yes. After it is connected, supported Torq 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.