Automate Ritc

What Ritc is

Rules in the Cloud

API host: api.ritc.io

What HumDay can do in Ritc

37 documented operations change something in Ritc.

• POSTCreate a new App User/users
• POSTCreate a channel/channels
• POSTAssign a channel to a user/users/{user_id}/channels
• POSTCreate a new app/apps
• POSTCreate a new rule/rules
• POSTCreate a new action/actions
• DELETERemove a user channel assignment/users/{user_id}/channels/{channel_id}
• POSTCreate a new trigger in an app/triggers
• POSTCreate a channel function/channels/{channel_id}/functions
• POSTCreate user channel/apps/channels/{channel_id}/users/{user_id}
• DELETERemove a user/users/{user_id}
• PATCHUpdate information about an App User/users/{user_id}
• DELETEDelete a channel/channels/{channel_id}
• PATCHUpdate a channel/channels/{channel_id}
• POSTCreate an org/orgs
• POSTCreate new external credentials/apps/ext/api/credentials
• POSTAuthenticate a user for a channel/users/authenticate/{user_id}/channel/{channel_id}
• DELETERemove a rule user/users/{user_id}/rules/{rule_id}
• POSTAssign a user to a rule/users/{user_id}/rules/{rule_id}
• POSTCreate a new admin user/users/admin
• POSTRun rule for a user/users/{user_id}/rules/{rule_id}/run
• DELETEDelete an app/apps/{app_id}
• PATCHUpdate an app/apps/{app_id}
• DELETEDelete a rule/rules/{rule_id}
• PATCHUpdate information about a specific rule/rules/{rule_id}
• DELETEDelete an action/actions/{action_id}
• PATCHUpdate information about a specific action/actions/{action_id}
• POSTRun active app rules/apps/rules/run
• DELETEDelete a trigger/triggers/{trigger_id}
• PATCHUpdate a trigger/triggers/{trigger_id}
• DELETEDelete credentials for a channel/apps/ext/api/credentials/{channel_id}
• PATCHUpdate credentials for a channel/apps/ext/api/credentials/{channel_id}
• POSTRun a rule/rules/{rule_id}/run
• POSTRun specified rule group in the app/apps/rulegroup/run/{rule_id_list}
• DELETERemove an admin user/users/admin/{user_id}
• PATCHUpdate information about an admin user/users/admin/{user_id}
• POSTLog a message/admin/log

What HumDay can read from Ritc

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

• GETGet a user channel/users/{user_id}/channels/{channel_id}
• GETChannels available to a User/users/{user_id}/channels
• GETGet user of a specified channel/apps/channels/{channel_id}/users/{user_id}
• GETGet users of a specified channel/apps/channels/{channel_id}/users
• GETGet an App User/users/{user_id}
• GETGet channel information/channels/{channel_id}
• GETGet app channels/apps/channels/users
• GETList rules/rules
• GETUsers/users
• GETList actions/actions
• GETRetrieve Channels/channels
• GETRules for a User/users/{user_id}/rules
• GETRetrieve Channel Functions/channels/{channel_id}/functions
• GETRetrieve Channels anonymously/channels/anonymous
• GETGet a user/users/{user_id}/rules/{rule_id}
• GETGet apps information/apps
• GETTriggers in an app/triggers
• GETGet channel function information/channels/{channel_id}/functions/{function_id}
• GETGet org information/orgs/me
• GETGet app information/apps/{app_id}
• GETGet a rule/rules/{rule_id}
• GETGet an action/actions/{action_id}
• GETGet a trigger/triggers/{trigger_id}
• GETGet credentials for a channel in an app/apps/ext/api/credentials/{channel_id}
• GETGet external credentials/apps/ext/api/credentials
• GETGet an admin user/users/admin/{user_id}
• GETAdmin users/users/admin
• GETPing the server/admin
• GETPing the server/admin/ping

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

Automate Ritc with these

• Cloudflare3122 operations
• Netboxdemo NetBox386 operations
• Linode342 operations
• Clever Cloud324 operations
• DRACOON276 operations
• Box Platform258 operations
• Netlify's documentation120 operations
• Meshery .75 operations
• Microsoft Custom Vision Training Client48 operations
• Turbinelabs Turbine Labs44 operations
• Ably Control22 operations
• Ably Platform22 operations

Categories

• Cloud

Questions about Ritc automation

Can HumDay connect to Ritc?

Yes. HumDay reads Ritc's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 66 operations are documented.

Do I need to write code to automate Ritc?

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 Ritc account.

What can HumDay do in Ritc?

37 of the 66 documented operations change something in Ritc, and 29 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Ritc 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 Ritc is held behind that approval.

Where this came from

The operations above are read from a published API description for Ritc at www.ritc.io/openapi/ritc.swagger.json. Descriptions are the provider’s own words, not ours. Last published 2017-04-04.