Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 19 Packages Projects Releases Wiki Activity

Clarify API key requirements for Fleet integration (#44551)

Browse Source 
Added note about required user role for MDM commands.
This commit is contained in:
Katheryn Satterlee
2026-05-05 09:50:15 -05:00
committed by GitHub
parent 227e94de5b
commit dd6f0795fe
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/building-webhook-flows-with-fleet-and-tines.md
+1 -1
View File
@@ -110,7 +110,7 @@ Next, we need to get more details about the device from Fleet. Devices are calle
_Tines HTTP Request action to get Fleet device details._
To access Fleet’s API, we need to provide an API key. We store the API key as a CREDENTIAL in the current story. The API key should belong to an API-only user in Fleet so that the key does not reset when the user logs out.
To access Fleet’s API, we need to provide an API key. We store the API key as a CREDENTIAL in the current story. The API key should belong to an API-only user in Fleet so that the key does not reset when the user logs out. Since we are running MDM commands in this workflow, the user will need a global role of Maintainer or Admin.
![Add credential to Tines story](../website/assets/images/articles/building-webhook-flows-with-fleet-and-tines-3-417x645@2x.png "Add credential to Tines story")