Automate IllumiDesk

What HumDay can do in IllumiDesk

86 documented operations change something in IllumiDesk. The 66 most useful are listed here.

• POSTCreate new user/v1/users/profiles/
• POSTCreate an email address/v1/users/{user}/emails/
• DELETEDelete an email address/v1/users/{user}/emails/{email_id}/
• PATCHUpdate an email address/v1/users/{user}/emails/{email_id}/
• PUTReplace an email address/v1/users/{user}/emails/{email_id}/
• POSTCreate a new team/v1/teams/
• POSTCreate a new server size item/v1/servers/options/server-size/
• PATCHUpdate a project file/v1/users/{user}/avatar/
• POSTAdd user avatar/v1/users/{user}/avatar/
• POSTCreate a new project/v1/{namespace}/projects/
• POSTRegister a user/auth/register/
• DELETEDelete avatar/v1/users/{user}/avatar/
• POSTCreate JSON Web Token (JWT)/auth/jwt-token-auth/
• DELETEDelete a user/v1/users/profiles/{user}/
• PATCHUpdate a user/v1/users/profiles/{user}/
• POSTCreate global notification settings/v1/{namespace}/notifications/settings/
• POSTRecreate an SSH key/v1/users/{user}/ssh-key/reset/
• PATCHMark a list of notifications as either read or unread./v1/{namespace}/notifications/
• POSTCreate a new server/v1/{namespace}/projects/{project}/servers/
• POSTCreate a new deployment/v1/{namespace}/projects/{project}/deployments/
• POSTCreate project files/v1/{namespace}/projects/{project}/project_files/
• POSTValidate JSON Web Token (JWT)/auth/jwt-token-verify/
• POSTRefresh a JSON Web Token (JWT)/auth/jwt-token-refresh/
• POSTAdd user to group/v1/teams/{team}/groups/{group}/add/
• PATCHModify global notification settings./v1/{namespace}/notifications/settings/
• POSTCreate global notification settings/v1/{namespace}/notifications/settings/entity/{entity}
• DELETEDelete a team/v1/teams/{team}/
• PATCHUpdate a team/v1/teams/{team}/
• PUTReplace a team/v1/teams/{team}/
• PATCHMark a specific notification as either read or unread./v1/{namespace}/notifications/{notification_id}
• PATCHMark a list of notifications as either read or unread./v1/{namespace}/notifications/entity/{entity}
• POSTCreate project collaborators/v1/{namespace}/projects/{project}/collaborators/
• POSTCreate a new server trigger/v1/{namespace}/projects/{project}/servers/{server}/triggers/
• POSTCreate a new server's run statistics/v1/{namespace}/projects/{project}/servers/{server}/run-stats/
• POSTUser removed from group/v1/teams/{team}/groups/{group}/remove/
• POSTCopy a project to your own account./v1/{namespace}/projects/project-copy/
• PATCHModify global notification settings./v1/{namespace}/notifications/settings/entity/{entity}
• DELETEDelete a project/v1/{namespace}/projects/{project}/
• PATCHUpdate a project/v1/{namespace}/projects/{project}/
• PUTReplace a project/v1/{namespace}/projects/{project}/
• DELETEDelete a server size by id/v1/servers/options/server-size/{size}/
• PATCHUpdate a server size by id/v1/servers/options/server-size/{size}/
• PUTReplace a server size by id/v1/servers/options/server-size/{size}/
• DELETEDelete a project file/v1/{namespace}/projects/{project}/project_files/{id}/
• PATCHUpdate a project file/v1/{namespace}/projects/{project}/project_files/{id}/
• PUTReplace a project file/v1/{namespace}/projects/{project}/project_files/{id}/
• DELETEDelete team group/v1/teams/{team}/groups/{group}/
• PATCHPatch team group/v1/teams/{team}/groups/{group}/
• PUTPatch team group/v1/teams/{team}/groups/{group}/
• POSTCreate a new subscription/v1/{namespace}/billing/subscriptions/
• POSTCreate SSH Tunnel associated to a server/v1/{namespace}/projects/{project}/servers/{server}/ssh-tunnels/
• POSTCreate a new team subscription/v1/teams/{team}/billing/subscriptions/
• DELETEDelete a server/v1/{namespace}/projects/{project}/servers/{server}/
• PATCHUpdate a server/v1/{namespace}/projects/{project}/servers/{server}/
• PUTReplace a server/v1/{namespace}/projects/{project}/servers/{server}/
• DELETEDelete a deployment/v1/{namespace}/projects/{project}/deployments/{deployment}/
• PATCHUpdate a deployment/v1/{namespace}/projects/{project}/deployments/{deployment}/
• PUTReplace a deployment/v1/{namespace}/projects/{project}/deployments/{deployment}/
• DELETEDelete a project collaborator/v1/{namespace}/projects/{project}/collaborators/{collaborator}/
• PATCHUpdate project collaborator/v1/{namespace}/projects/{project}/collaborators/{collaborator}/
• POSTCreate new credit card/v1/{namespace}/billing/cards/
• POSTCreate a new OAuth2 application/v1/{namespace}/oauth/applications/
• POSTServer api key validation/v1/{namespace}/projects/{project}/servers/{server}/auth/
• POSTStop a server/v1/{namespace}/projects/{project}/servers/{server}/stop/
• POSTStart a server/v1/{namespace}/projects/{project}/servers/{server}/start/
• POSTDeploy an existing model/v1/{namespace}/projects/{project}/deployments/{deployment}/deploy/

What HumDay can read from IllumiDesk

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

• GETRetrieve account email addresses/v1/users/{user}/emails/
• GETGet user list/v1/users/profiles/
• GETRetrieve a user's email addresses/v1/users/{user}/emails/{email_id}/
• GETA convenience endpoint that is equivalent to GET /v1/users/profiles/ //v1/me
• GETRetrieve user's avatar/v1/users/{user}/avatar/
• GETRetrieve account's API key/v1/users/{user}/api-key/
• GETRetrieve an SSH key/v1/users/{user}/ssh-key/
• GETRetrieve a user/v1/users/profiles/{user}/
• GETRetrieve global notification settings for the authenticated user/v1/{namespace}/notifications/settings/
• GETGet a search results/v1/{namespace}/search/
• GETGet notifications of all types and entities for the authenticated user./v1/{namespace}/notifications/
• GETGet teams/v1/teams/
• GETRetrieve global notification settings for the authenticated user/v1/{namespace}/notifications/settings/entity/{entity}
• GETGet a team/v1/teams/{team}/
• GETRetrieve a specific notification./v1/{namespace}/notifications/{notification_id}
• GETGet available projects/v1/{namespace}/projects/
• GETRetrieve available server sizes/v1/servers/options/server-size/
• GETGet notifications of all types and entities for the authenticated user./v1/{namespace}/notifications/entity/{entity}
• GETGet project files/v1/{namespace}/projects/{project}/project_files/
• GETGet team groups/v1/teams/{team}/groups/
• GETGet a project/v1/{namespace}/projects/{project}/
• GETGet a server size by id/v1/servers/options/server-size/{size}/
• GETGet a project file/v1/{namespace}/projects/{project}/project_files/{id}/
• GETGet team group/v1/teams/{team}/groups/{group}/
• GETRetrieve servers/v1/{namespace}/projects/{project}/servers/
• GETRetrieve deployments/v1/{namespace}/projects/{project}/deployments/
• GETGet project collaborators/v1/{namespace}/projects/{project}/collaborators/
• GETRetrieve server statuses/v1/{namespace}/projects/{project}/servers/statuses/
• GETRetrieve a server/v1/{namespace}/projects/{project}/servers/{server}/
• GETRetrieve a deployment/v1/{namespace}/projects/{project}/deployments/{deployment}/
• GETGet a project collaborator/v1/{namespace}/projects/{project}/collaborators/{collaborator}/
• GETGet server API key/v1/{namespace}/projects/{project}/servers/{server}/api-key/
• GETRetrieve server triggers/v1/{namespace}/projects/{project}/servers/{server}/triggers/
• GETGet SSH Tunnels associated to a server/v1/{namespace}/projects/{project}/servers/{server}/ssh-tunnels/

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

Automate IllumiDesk with these

• Monarchinitiative BioLink164 operations
• UniCourt Enterprise158 operations
• OSF APIv2 Documentation156 operations
• Figshare136 operations
• MCW Rat Genome Database100 operations
• U.S. EPA Enforcement and Compliance History Online (ECHO) Detailed Facility Report (DFR)94 operations
• OpenFEC91 operations
• NBA Stats83 operations
• Thebluealliance The Blue Alliance65 operations
• eDRV57 operations
• Collegefootballdata College Football Data51 operations
• Dnd5eapi D&D 5e47 operations

Categories

• Open data

Questions about IllumiDesk automation

Can HumDay connect to IllumiDesk?

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

Do I need to write code to automate IllumiDesk?

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

What can HumDay do in IllumiDesk?

86 of the 143 documented operations change something in IllumiDesk, and 57 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Where this came from

The operations above are read from a published API description for IllumiDesk at raw.githubusercontent.com/3Blades/openapi/master/tbs_swagger.yml. Descriptions are the provider’s own words, not ours. Last published 2018-02-19.