Automate Journy Developer documentation
HumDay reads Journy Developer documentation’s own published API description and derives 15 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 Journy Developer documentation is
# Welcome Implementing a new tool can be daunting, but it doesn't have to. You can implement journy.io in a few different ways to ensure it fits with the rest of your tech stack seamlessly. We welcome your feedback, ideas and suggestions. We really want to make your life easier, so if we’re falling short or should be doing something different, we want to hear about it. Send us an email at [hi@jour
API host: api.journy.io
What HumDay can do in Journy Developer documentation
8 documented operations change something in Journy Developer documentation.
- POSTCreate or update user
/users/upsert - POSTLink web activity to user
/link - DELETEDelete user
/users - POSTAdd users to an account
/accounts/users/add - POSTRemove user from account
/accounts/users/remove - POSTTrack event
/track - POSTCreate or update account
/accounts/upsert - DELETEDelete account
/accounts
What HumDay can read from Journy Developer documentation
These are the operations a schedule or a trigger can watch.
- GETGet user segments
/segments/users - GETGet user properties
/properties/users - GETGet events
/events - GETValidate API key
/validate - GETGet snippet for a website
/tracking/snippet - GETGet account segments
/segments/accounts - GETGet account properties
/properties/accounts
How automating Journy Developer documentation 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 Journy Developer documentation account.
- Grant access, then go live. You approve the specific Journy Developer documentation operations it may use — and only those.
Automate Journy Developer documentation with these
- Zendesk636 operations
- Drchrono263 operations
- Pipedrive196 operations
- SalesLoft Platform118 operations
- Intercom108 operations
- Attio90 operations
- Orbit33 operations
- HubSpot Contacts13 operations
- HubSpot Companies12 operations
- HubSpot Deals12 operations
- HubSpot Tickets12 operations
- Roaring CompanyAPI11 operations
Categories
Questions about Journy Developer documentation automation
- Can HumDay connect to Journy Developer documentation?
- Yes. HumDay reads Journy Developer documentation's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 15 operations are documented.
- Do I need to write code to automate Journy Developer documentation?
- 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 Journy Developer documentation account.
- What can HumDay do in Journy Developer documentation?
- 8 of the 15 documented operations change something in Journy Developer documentation, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Journy Developer documentation 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 Journy Developer documentation is held behind that approval.
Where this came from
The operations above are read from a published API description for Journy Developer documentation at api.journy.io/spec.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.