- HTTP request
- Path parameters
- Request body
- Response body
- Authorization scopes
- PlaybookImportStrategy
- Try it!
Imports the specified playbook to the specified agent from a binary file.
HTTP request
POST https://{endpoint}/v3beta1/{parent=projects/*/locations/*/agents/*}/playbooks:import
Where {endpoint}
is one of the supported service endpoints.
The URLs use gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
parent |
Required. The agent to import the playbook into. Format: Authorization requires the following IAM permission on the specified resource
|
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "importStrategy": { object ( |
Fields | |
---|---|
import |
Optional. Specifies the import strategy used when resolving resource conflicts. |
Union field Dialogflow performs a read operation for the Cloud Storage object on the caller's behalf, so your request authentication must have read permissions for the object. For more information, see |
|
playbook |
|
playbook |
Uncompressed raw byte content for playbook. A base64-encoded string. |
Response body
If successful, the response body contains an instance of Operation
.
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/cloud-platform
https://www.googleapis.com/auth/dialogflow
For more information, see the Authentication Overview.
PlaybookImportStrategy
The playbook import strategy used for resource conflict resolution associated with an ImportPlaybookRequest
.
JSON representation |
---|
{ "mainPlaybookImportStrategy": enum ( |
Fields | |
---|---|
main |
Optional. Specifies the import strategy used when resolving conflicts with the main playbook. If not specified, 'CREATE_NEW' is assumed. |
nested |
Optional. Specifies the import strategy used when resolving referenced playbook/flow conflicts. If not specified, 'CREATE_NEW' is assumed. |
tool |
Optional. Specifies the import strategy used when resolving tool conflicts. If not specified, 'CREATE_NEW' is assumed. This will be applied after the main playbook and nested resource import strategies, meaning if the playbook that references the tool is skipped, the tool will also be skipped. |