HumDay

Automate NRM Georg

HumDay reads NRM Georg’s own published API description and derives 5 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.

Automate NRM Georg

What HumDay can do in NRM Georg

1 documented operations change something in NRM Georg.

What HumDay can read from NRM Georg

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

How automating NRM Georg works

  1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
  2. 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.
  3. See it proven. The program runs and shows you the result before it is allowed near your live NRM Georg account.
  4. Grant access, then go live. You approve the specific NRM Georg operations it may use — and only those.

Automate NRM Georg with these

Categories

Questions about NRM Georg automation

Can HumDay connect to NRM Georg?
Yes. HumDay reads NRM Georg's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 5 operations are documented.
Do I need to write code to automate NRM Georg?
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 NRM Georg account.
What can HumDay do in NRM Georg?
1 of the 5 documented operations change something in NRM Georg, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my NRM Georg 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 NRM Georg is held behind that approval.

Where this came from

The operations above are read from a published API description for NRM Georg at georg.nrm.se/api/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.