HumDay

Automate OrgHunter

HumDay reads OrgHunter’s own published API description and derives 6 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 OrgHunter

What OrgHunter is

Get the latest IRS data and most up to date charity information for your website or application

API host: data.orghunter.com

What HumDay can do in OrgHunter

6 documented operations change something in OrgHunter.

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

Questions about OrgHunter automation

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

Where this came from

The operations above are read from a published API description for OrgHunter at orghunter.3scale.net/swagger/spec.json. Descriptions are the provider’s own words, not ours. Last published 2017-04-11.