Control D connector for Okou
Connect Control D to manage DNS filtering profiles, endpoints, resolver access, analytics, organizations, billing, and service catalogs.
Data & infrastructure · API Token
Use Control D in Okou
Control D API for managing DNS filtering profiles, endpoints, resolver access, analytics, organizations, billing, and service catalogs.
Once connected, supported Control D 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 Control D
- Read Control D account information.
- Enable or disable filters on a Control D profile.
- Read Control D endpoints and endpoint type options.
- Read IPs known to a Control D endpoint.
- Read available Control D analytics regions and log levels.
- Read Control D products, subscriptions, and payment data.
- Read Control D organization, member, and sub-organization data.
- Read the public Control D IP and network information routes.
How the Control D connector works
A connected service becomes one permissioned step in the work you hand off.
- 1
Connect Control D
Choose API Token.
- 2
Choose the work
Use only the supported actions your workflow needs.
- 3
Run it your way
Start it once, schedule it, or attach an event trigger.
Connect Control D securely
Use the connection method that fits your account and grant only the access the workflow needs.
- API 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.
What Control D covers
The topics this connector's published operations touch.
- dns
- dns filtering
- network security
- profiles
- endpoints
- analytics
Control D connector questions
- What can Okou do with Control D?
- Connect Control D to manage DNS filtering profiles, endpoints, resolver access, analytics, organizations, billing, and service catalogs. Documented actions include: Read Control D account information. Enable or disable filters on a Control D profile.
- How do I connect Control D to Okou?
- Connect Control D using API Token. The connection controls which supported actions a workflow can use.
- Can Control D run in an automated workflow?
- Yes. After it is connected, supported Control D 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.
Convex
Connect Convex to inspect projects, deployments, custom domains, audit logs, roles, and token metadata through its read-only Management API.
Context.dev
Connect Context.dev, formerly Brand.dev, to retrieve brand intelligence, scrape and extract web data, parse documents, run monitors, and process batches.
Coralogix
Connect Coralogix to run DataPrime and Lucene queries across logs, metrics, and spans.
