Method: actions.create

• HTTP request
• Path parameters
• Request body
• Response body
• Authorization scopes
• IAM Permissions

Full name: projects.locations.instances.integrations.actions.create

Creates a new custom IntegrationAction within an integration. Use this method to define a new automated task. Custom actions require a unique display name and a functional Python script, and are typically developed within the SecOps IDE.

HTTP request

Choose a location:

africa-south1 asia-northeast1 asia-south1 asia-southeast1 asia-southeast2 australia-southeast1 europe-central2 europe-west12 europe-west2 europe-west3 europe-west6 europe-west9 me-central1 me-central2 me-west1 northamerica-northeast2 southamerica-east1 us eu

POST https://chronicle.africa-south1.rep.googleapis.com/v1beta/{parent}/actions

Path parameters

Parameters
parent	string Required. The instance to create a IntegrationAction for. Format: projects/{project}/locations/{location}/instances/{instance}/soar/integrations/{integration}

Request body

The request body contains an instance of IntegrationAction.

Response body

If successful, the response body contains a newly created instance of IntegrationAction.

Authorization scopes

Requires one of the following OAuth scopes:

• https://www.googleapis.com/auth/cloud-platform
• https://www.googleapis.com/auth/chronicle
• https://www.googleapis.com/auth/chronicle.readonly

For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the parent resource:

• chronicle.integrationActions.update

For more information, see the IAM documentation.