Actions75
- EndpointAutopilot Actions
- TenantAdministrationAlerts Actions
- EndpointMEM Actions
- TenantGDAP Actions
- TenantAdministrationApplicationApproval Actions
- TenantAdministration Actions
- CIPPSetup Actions
- Security Actions
- IdentityAdministrationDevices Actions
- CIPPExtensions Actions
- EmailExchangeTools Actions
CIPPSetup → ExecCombinedSetup
AI-generatedOverview
The CIPPSetup - ExecCombinedSetup operation in this node allows users to perform a combined setup process for the CIPP platform by sending a POST request to the /api/ExecCombinedSetup endpoint. This operation is useful for initializing or configuring the CIPP environment with various parameters such as application credentials, baseline options, email, refresh tokens, selected baselines and options, tenant ID, and webhook URL. It is beneficial in scenarios where a comprehensive setup is required in a single API call, streamlining the configuration process for the CIPP platform.
Use Case Examples
- A user wants to configure the CIPP platform with specific application credentials and baseline options in one step.
- An administrator needs to update the refresh token and webhook URL for the CIPP setup in a single API request.
Properties
| Name | Meaning |
|---|---|
| Application Id | The application id used for authentication or identification in the setup process. |
| Application Secret | The secret key associated with the application id for secure authentication. |
| Baseline Option | The baseline option to specify configuration defaults or templates. |
| The email address associated with the setup or notifications. | |
| Refresh Token | The refresh token used for renewing authentication tokens. |
| Selected Baselines | The selected baselines to apply during the setup. |
| Selected Option | The selected option to customize the setup process. |
| Tenantid | The tenant identifier for which the setup is being performed. |
| Webhook | The webhook URL to receive callbacks or notifications. |
Output
JSON
debug- Debug information including actual URL, query parameters, headers, and body sent for each API request (if debug option is enabled).*- The JSON response from the API call, structure varies depending on the API response.
Dependencies
- An API key credential for CIPPApi to authenticate requests.
Troubleshooting
- Ensure all required fields such as applicationId, applicationSecret, tenantid, and refreshToken are correctly provided to avoid authentication errors.
- If the API request fails, check the debug output (if enabled) for the exact request details to diagnose issues.
- Network connectivity issues or incorrect endpoint URLs can cause request failures; verify network and endpoint configurations.