Automate Redhat Catalog Inventory

What Redhat Catalog Inventory is

Catalog Inventory

API host: cloud.redhat.com

What HumDay can do in Redhat Catalog Inventory

8 documented operations change something in Redhat Catalog Inventory.

• PATCHUpdate an existing Task/tasks/{id}
• POSTPerform a GraphQL Query/graphql
• POSTOrder an existing ServiceOffering/service_offerings/{id}/order
• PATCHRefresh an existing Source/sources/{id}/refresh
• POSTTag a ServiceInventory/service_inventories/{id}/tag
• POSTUntag a ServiceInventory/service_inventories/{id}/untag
• PATCHIncremental Refresh an existing Source/sources/{id}/incremental_refresh
• POSTInvokes computing of ServiceInventories tags for given ServiceOffering/service_offerings/{id}/applied_inventories_tags

What HumDay can read from Redhat Catalog Inventory

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

• GETList Tasks/tasks
• GETShow an existing Task/tasks/{id}
• GETList Tags/tags
• GETList Sources/sources
• GETList ServicePlans/service_plans
• GETList Tasks for Source/sources/{id}/tasks
• GETList ServiceInstances/service_instances
• GETList ServiceOfferings/service_offerings
• GETList ServiceCredentials/service_credentials
• GETList ServiceInventories/service_inventories
• GETList ServiceOfferingNodes/service_offering_nodes
• GETList ServiceCredentialTypes/service_credential_types
• GETReturn this API document in JSON format/openapi.json
• GETList ServicePlans for Source/sources/{id}/service_plans
• GETList Tags for ServiceInventory/service_inventories/{id}/tags
• GETList ServiceInstances for Source/sources/{id}/service_instances
• GETList ServiceOfferings for Source/sources/{id}/service_offerings
• GETList ServiceInventories for Source/sources/{id}/service_inventories
• GETList ServiceOfferingNodes for Source/sources/{id}/service_offering_nodes
• GETList ServicePlans for ServiceOffering/service_offerings/{id}/service_plans
• GETList ServiceInstances for ServiceOffering/service_offerings/{id}/service_instances
• GETList ServiceOfferingNodes for ServiceOffering/service_offerings/{id}/service_offering_nodes
• GETShow an existing Source/sources/{id}
• GETShow an existing ServicePlan/service_plans/{id}
• GETShow an existing ServiceInstance/service_instances/{id}
• GETShow an existing ServiceOffering/service_offerings/{id}
• GETShow an existing ServiceCredential/service_credentials/{id}
• GETShow an existing ServiceInventory/service_inventories/{id}
• GETShow an existing ServiceOfferingNode/service_offering_nodes/{id}
• GETShow an existing ServiceCredentialType/service_credential_types/{id}

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

Popular Redhat Catalog Inventory integrations

Connect Redhat Catalog Inventory to the tools people pair it with most.

• Redhat Catalog Inventory and OData for namespace microsoft.graphintegration
• Redhat Catalog Inventory and Cloudflareintegration
• Redhat Catalog Inventory and NetBoxintegration
• Redhat Catalog Inventory and GitHubintegration
• Redhat Catalog Inventory and Mistintegration
• Redhat Catalog Inventory and Loket.nlintegration
• Redhat Catalog Inventory and Atlassian The Jira Cloud platformintegration
• Redhat Catalog Inventory and Magento B2Bintegration
• Redhat Catalog Inventory and Stripeintegration
• Redhat Catalog Inventory and Zuora Reference Billingintegration
• Redhat Catalog Inventory and bunqintegration
• Redhat Catalog Inventory and DocuSignintegration

Automate Redhat Catalog Inventory with these

• Redhat Patchman engine21 operations
• OData for namespace microsoft.graph11412 operations
• GitHub811 operations
• Atlassian The Jira Cloud platform474 operations
• Gitlab358 operations
• JIRA 7.6.1324 operations
• Appcenter App Center Client323 operations
• Gitea .321 operations
• Bitbucket292 operations
• Keycloak Admin281 operations
• Apple App Store Connect251 operations
• Files.com222 operations

Categories

• Developer tools

Questions about Redhat Catalog Inventory automation

Can HumDay connect to Redhat Catalog Inventory?

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

Do I need to write code to automate Redhat Catalog Inventory?

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 Redhat Catalog Inventory account.

What can HumDay do in Redhat Catalog Inventory?

8 of the 38 documented operations change something in Redhat Catalog Inventory, and 30 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Where this came from

The operations above are read from a published API description for Redhat Catalog Inventory at raw.githubusercontent.com/RedHatInsights/catalog_inventory-api/master/public/doc/openapi-3. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.