Can HumDay connect to Truora Checks?

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

Do I need to write code to automate Truora Checks?

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 Truora Checks account.

What can HumDay do in Truora Checks?

13 of the 25 documented operations change something in Truora Checks, and 12 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Truora Checks 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 Truora Checks is held behind that approval.

Automate Truora Checks

HumDay reads Truora Checks’s own published API description and derives 25 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 Truora Checks is

**NOTE:** This is a preview of the API and it is not considered stable since refinements are still being made. # Introduction Welcome to the **Truora Check** [**RESTful API**](https://en.wikipedia.org/wiki/Representational_state_transfer) reference. You may also want to check out our [**Validations API docs**](https://docs.validations.truora.com/) or our [**Signals API docs**](https://docs.signals

API host: api.truora.com

What HumDay can do in Truora Checks

13 documented operations change something in Truora Checks.

POSTCreates a hook subscription/v1/hooks
POSTCreate a background check/v1/checks
POSTCreate Score Configurations/v1/config
POSTCreate Report/v1/reports
POSTCreates a continuous check that will run background checks recurrently according to the frequency provided./v1/continuous-checks
DELETEDelete Custom Type/v1/config
PUTUpdate Custom Type/v1/config
POSTReport Behavior/v1/behavior
POSTCreate PDF/v1/checks/{check_id}/pdf
POSTBatch Upload/v1/reports/{report_id}/upload
DELETEDeletes hook/v1/hooks/{hook_id}
PUTUpdates hook/v1/hooks/{hook_id}
PUTUpdates a continuous check/v1/continuous-checks/{continuous_check_id}

What HumDay can read from Truora Checks

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

GETList Checks/v1/checks
GETList Score Configurations/v1/config
GETList Reports/v1/reports
GETLists all hooks/v1/hooks
GETLists all continuous checks/v1/continuous-checks
GETList Check Details/v1/checks/{check_id}/details
GETGet Health Dashboard/v1/checks/health
GETGet Background Check/v1/checks/{check_id}
GETGet Report/v1/reports/{report_id}
GETLists history associated with a Check./v1/continuous-checks/{continuous_check_id}
GETGet PDF/v1/checks/{check_id}/pdf
GETLists background check logs./v1/continuous-checks/{continuous_check_id}/history

How automating Truora Checks 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 Truora Checks account.
Grant access, then go live. You approve the specific Truora Checks operations it may use — and only those.