Conversation
…pdate docs Co-authored-by: Vinícius <36349314+vrmiguel@users.noreply.github.com>
|
Requesting review from @DarrenBaldwin07 who has experience with the following files modified in this PR:
|
features/automations.mdx
Outdated
|
|
||
| 1. Set a **Slug** on your automation (in the automation's properties panel). | ||
| 2. Trigger the automation with that slug from API calls or slash commands. | ||
| 2. Trigger the automation with that slug or its UUID from API calls or slash commands. |
There was a problem hiding this comment.
Drop step 1, make the page only mention the UUIDs
There was a problem hiding this comment.
Looking at the diff, it appears no changes were made to address this feedback yet.
I'll need to remove step 1 (the slug setup instruction) and update the content to only reference UUIDs for triggering automations.
features/automations.mdx
Outdated
|
|
||
| The API key can be supplied either through the `Authorization: Bearer` header or the `apiKey` query parameter: | ||
|
|
||
| ```bash |
There was a problem hiding this comment.
Drop these, only refer to the API docs
There was a problem hiding this comment.
The diff appears to be empty, so it looks like no changes were made yet to address this. I'll remove the API key supply details and defer to the API docs instead.
…plify auth examples Co-authored-by: Vinícius <36349314+vrmiguel@users.noreply.github.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Summary
Updated the automation trigger endpoint to accept either workflow UUID or slug (key). Changes include:
Backend (monorepo):
/automation/:keyOrId/triggerroute to accept both UUID and slugDocumentation (docs):
${AUTOMATION_ID}(UUID) instead of slugAuthorization: BearerheaderapiKeyquery parameterRelated Pull Requests