Automate Greip
HumDay reads Greip’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.
What Greip is
This documentation shows how to use Greip API, By highlighting the API methods, options and some other features that allow you to get the most of this API.
API host: gregeoip.com
What HumDay can read from Greip
These are the operations a schedule or a trigger can watch.
- GETbadWords endpoint: Detects whether user inputs contain profanity or not.
/badWords - GETGeoIP endpoint: Returns the geolocation data of the visitor.
/GeoIP - GETCountry endpoint: Returns the information of a specific country by passing the countrCode.
/Country - GETIPLookup endpoint: Returns the geolocation data of a specific IP Address.
/IPLookup - GETBulkLookup endpoint: Returns the geolocation data of multiple IP Addresses.
/BulkLookup
How automating Greip 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 Greip account.
- Grant access, then go live. You approve the specific Greip operations it may use — and only those.
Questions about Greip automation
- Can HumDay connect to Greip?
- Yes. HumDay reads Greip'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 Greip?
- 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 Greip account.
- What can HumDay do in Greip?
- 0 of the 5 documented operations change something in Greip, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Greip 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 Greip is held behind that approval.
Where this came from
The operations above are read from a published API description for Greip at greip.io/OpenAPI.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.