Enables providers to create or modify one or multiple assets with a single order payload from an external system. Automatically detects products set in the payload. No limits for the maximum number, but at one item of one product needs to be present.For a given product, automatically detects if a new asset needs to be created or existing needs to be adjusted by searching via external asset id.
Vendors can use this action to approve pending Tier Configuration Requests.
Allows the creation of a single request of type “change” on a existing asset in CloudBlue Connect. The asset identifier can be passed from previous steps of the Zap.
Allows the creation of a single request of type “resume” on a existing asset in CloudBlue Connect. The asset identifier can be passed from previous steps of the Zap.
Vendors and providers can use this actions to add messages to conversations on multiple objects like asset requests, this messages can be seen by vendors and providers and can provide valuable information like reason why a request has not been approved.
Providers can create Update Tier Config Requests for existing Tier Configs, the Tier Config ID is required and can be obtained using the search, the list of parameters to update may come from previous step of the Zap due line item support, please note that only ordering type parameters can be updated.
Vendors can use this action to populate values for Fulfillment parameters on Asset requests that are in pending status, the values can come from previous steps.
Vendors can use this action to populate values for Fulfillment parameters on Tier Config Requests knowing the list of parameters they want to populate, the values can come from previous steps.
Vendors can use this action to inquire a pending request knowing the concrete request parameters they want to inquire for.
Vendors can use this action to inquire a pending Tier Config Request for parameters obtained on previous steps of the zap, like for example when interacting with Vendor API and API can define multiple fields that requires refinement.
Vendors can use this action to approve a concrete request that is in status pending.
Providers and Vendors can use this action to reject a concrete request.
Providers can create cancel requests using this action, in order to cancel an asset.
Providers can create purchase requests using this action, action has line items support to add multiple items or set multiple parameters of ordering type together with the request.
Allows the creation of a single request of type “suspend” on a existing asset in CloudBlue Connect. The asset identifier can be passed from previous steps of the Zap.
Providers can create Update Tier Config Requests for existing Tier Configs, the Tier Config ID is required and can be obtained using the search, the list of parameters to update must be known and could be all of type order.
Vendors can use this action to Reject Tier Configuration Requests.
Vendors can use this action to populate values for Fulfillment parameters on Asset requests that are in pending status, with the help of line items support is possible to populate them dynamically and populate the ones resulting from previous steps of the Zap.
Vendors can use this action to populate values for Fulfillment parameters on Tier Config Requests, with the help of line items support is possible to populate them dynamically and populate the ones resulting from previous steps of the Zap.
Vendors can use this action to inquire a request setting multiple parameters that needs changes, this action is useful when external systems can define the list of parameters to inquire for.
Vendors can use this action to inquire a pending Tier Config Request for parameters obtained on previous steps of the zap, like for example when interacting with Vendor API and API can define multiple fields that requires refinement.
English
Arabic
Chinese (Simplified)
Dutch
French
German
Italian
Portuguese
Russian
Spanish