From b1fd64df3a3e70ed1e567d520a903309f5a0eea9 Mon Sep 17 00:00:00 2001 From: Slack API Ref Buildbot Date: Sat, 17 Feb 2024 22:29:06 +0000 Subject: [PATCH] Updated from Slack docs, 2024/02/17 --- ....workflows.triggers.types.permissions.json | 3 + ...kflows.triggers.types.permissions.set.json | 63 +++++++++++++++++++ 2 files changed, 66 insertions(+) create mode 100644 groups/admin.workflows.triggers.types.permissions.json create mode 100644 methods/admin/admin.workflows.triggers.types.permissions.set.json diff --git a/groups/admin.workflows.triggers.types.permissions.json b/groups/admin.workflows.triggers.types.permissions.json new file mode 100644 index 00000000..9285bfbb --- /dev/null +++ b/groups/admin.workflows.triggers.types.permissions.json @@ -0,0 +1,3 @@ +{ + "name": "admin.workflows.triggers.types.permissions" +} \ No newline at end of file diff --git a/methods/admin/admin.workflows.triggers.types.permissions.set.json b/methods/admin/admin.workflows.triggers.types.permissions.set.json new file mode 100644 index 00000000..0b959d00 --- /dev/null +++ b/methods/admin/admin.workflows.triggers.types.permissions.set.json @@ -0,0 +1,63 @@ +{ + "group": "admin", + "name": "admin.workflows.triggers.types.permissions.set", + "deprecated": false, + "desc": "Set the permissions for using a trigger type in workflow builder", + "args": { + "id": { + "required": true, + "example": "['FTT01', 'FTT02', 'FTT03']", + "desc": "The trigger type ID for which to set the permissions." + }, + "visibility": { + "required": true, + "desc": "The function visibility.", + "type": "enum" + }, + "user_ids": { + "required": false, + "example": "['U00000001', 'U00000002', 'U00000003']", + "desc": "List of user IDs to allow for named_entities visibility.", + "type": "array" + } + }, + "response": { + "examples": [ + + ] + }, + "errors": { + "access_denied": "Access to a resource specified in the request is denied.", + "trigger_type_id_not_found": "The referenced trigger type ID does not exist.", + "visibility_is_not_named_entities": "The visibility should be named enitites when the user_ids, team_ids, or org_ids args are set.", + "account_inactive": "Authentication token is for a deleted user or workspace when using a bot token.", + "deprecated_endpoint": "The endpoint has been deprecated.", + "ekm_access_denied": "Administrators have suspended the ability to post a message.", + "enterprise_is_restricted": "The method cannot be called from an Enterprise.", + "invalid_auth": "Some aspect of authentication cannot be validated. Either the provided token is invalid or the request originates from an IP address disallowed from making the request.", + "is_bot": "This method cannot be called by a legacy bot.", + "method_deprecated": "The method has been deprecated.", + "missing_scope": "The token used is not granted the specific scope permissions required to complete this request.", + "not_allowed_token_type": "The token type used in this request is not allowed.", + "not_authed": "No authentication token provided.", + "no_permission": "The workspace token used in this request does not have the permissions necessary to complete the request. Make sure your app is a member of the conversation it's attempting to post a message to.", + "org_login_required": "The workspace is undergoing an enterprise migration and will not be available until migration is complete.", + "token_expired": "Authentication token has expired.", + "token_revoked": "Authentication token is for a deleted user or workspace or the app has been removed when using a user token.", + "two_factor_setup_required": "Two factor setup is required.", + "accesslimited": "Access to this method is limited on the current network.", + "fatal_error": "The server could not complete your operation(s) without encountering a catastrophic error. It's possible some aspect of the operation succeeded before the error was raised.", + "internal_error": "The server could not complete your operation(s) without encountering an error, likely due to a transient issue on our end. It's possible some aspect of the operation succeeded before the error was raised.", + "invalid_arg_name": "The method was passed an argument whose name falls outside the bounds of accepted or expected values. This includes very long names and names with non-alphanumeric characters other than _. If you get this error, it is typically an indication that you have made a very malformed API call.", + "invalid_arguments": "The method was either called with invalid arguments or some detail about the arguments passed is invalid, which is more likely when using complex arguments like blocks or attachments.", + "invalid_array_arg": "The method was passed an array as an argument. Please only input valid strings.", + "invalid_charset": "The method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8 iso-8859-1.", + "invalid_form_data": "The method was called via a POST request with Content-Type application/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.", + "invalid_post_type": "The method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/json application/x-www-form-urlencoded multipart/form-data text/plain.", + "missing_post_type": "The method was called via a POST request and included a data payload, but the request did not include a Content-Type header.", + "ratelimited": "The request has been ratelimited. Refer to the Retry-After header for when to retry the request.", + "request_timeout": "The method was called via a POST request, but the POST data was either missing or truncated.", + "service_unavailable": "The service is temporarily unavailable.", + "team_added_to_org": "The workspace associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete." + } +} \ No newline at end of file