Can HumDay connect to .clarify.io?

Yes. HumDay reads .clarify.io's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 21 operations are documented.

Do I need to write code to automate .clarify.io?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your .clarify.io account.

What can HumDay do in .clarify.io?

11 of the 21 documented operations change something in .clarify.io, and 10 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my .clarify.io account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to .clarify.io is held behind that approval.

Automate .clarify.io

HumDay reads .clarify.io’s own published API description and derives 21 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What .clarify.io is

The API to Search and Understand Audio & Video Data.

API host: api.clarify.io

What HumDay can do in .clarify.io

11 documented operations change something in .clarify.io.

POSTCreate a bundle/v1/bundles
POSTAdd a track for a bundle/v1/bundles/{bundle_id}/tracks
DELETEDelete a bundle/v1/bundles/{bundle_id}
PUTUpdate a bundle/v1/bundles/{bundle_id}
PUTAdd media to a track/v1/bundles/{bundle_id}/tracks/{track_id}
DELETEDelete bundle tracks/v1/bundles/{bundle_id}/tracks
PUTUpdate a tracks for a bundle/v1/bundles/{bundle_id}/tracks
POSTRequest an insight to be run/v1/bundles/{bundle_id}/insights
DELETEDelete bundle metadata/v1/bundles/{bundle_id}/metadata
PUTUpdate bundle metadata/v1/bundles/{bundle_id}/metadata
DELETEDelete a bundle track/v1/bundles/{bundle_id}/tracks/{track_id}

What HumDay can read from .clarify.io

These are the operations a schedule or a trigger can watch.

GETSearch bundles/v1/search
GETList bundles/v1/bundles
GETGenerate Group Report beta/v1/reports/scores
GETGenerate Trends Report beta/v1/reports/trends
GETGet a bundle/v1/bundles/{bundle_id}
GETGet bundle tracks/v1/bundles/{bundle_id}/tracks
GETGet bundle insights/v1/bundles/{bundle_id}/insights
GETGet bundle metadata/v1/bundles/{bundle_id}/metadata
GETGet bundle track/v1/bundles/{bundle_id}/tracks/{track_id}
GETGet bundle insight/v1/bundles/{bundle_id}/insights/{insight_id}

How automating .clarify.io works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live .clarify.io account.
Grant access, then go live. You approve the specific .clarify.io operations it may use — and only those.