Allows an arbitrary filter to be specified and applied in Turbinelabs Turbine Labs

What this operation does

Allows an arbitrary filter to be specified and applied to the org\'s change log.

• GETReads data · Audit Logapi.turbinelabs.io/changelog/adhoc

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Turbinelabs Turbine Labs operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Turbinelabs Turbine Labs operations

• Create proxyPOST · changes data
• Create routePOST · changes data
• Create domainPOST · changes data
• Create clusterPOST · changes data
• Create listenerPOST · changes data
• Create sharedrulesPOST · changes data
• Add instancePOST · changes data
• Delete proxyDELETE · changes data

All 44 Turbinelabs Turbine Labs operations

Questions

Can HumDay allows an arbitrary filter to be specified and applied in Turbinelabs Turbine Labs?

Yes. This operation is published in Turbinelabs Turbine Labs's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my Turbinelabs Turbine Labs account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Turbinelabs Turbine Labs.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Turbinelabs Turbine Labs account.

Where this came from

Read from a published API description for Turbinelabs Turbine Labs at raw.githubusercontent.com/turbinelabs/api/master/swagger.yml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.