Creates a UserOrganization resource in redirection.io
A documented redirection.io operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Creates a UserOrganization resource.
- POSTChanges data · UserOrganization
api.redirection.io/user-organizations
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which redirection.io operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other redirection.io operations
- Creates a User resourcePOST · changes data
- Creates a AgentFlushRequest resourcePOST · changes data
- Creates a UserProject resourcePOST · changes data
- Replaces the User resourcePUT · changes data
- Removes the User resourceDELETE · changes data
- Creates a ForgotPasswordRequest resourcePOST · changes data
- Creates a Crawl resourcePOST · changes data
- Creates a Import resourcePOST · changes data
Questions
- Can HumDay creates a userorganization resource in redirection.io?
- Yes. This operation is published in redirection.io's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my redirection.io data?
- Yes — this is a POST operation, so it changes something in redirection.io. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your redirection.io account.
Where this came from
Read from a published API description for redirection.io at api.redirection.io/docs.json. The description above is the provider’s own wording, not ours. Last published 2019-09-23.