RMM & Endpoint

Action1

Run Action1 patch, software, and endpoint operations from plain-language requests.

Dex connects to Action1 over the REST API 3.0 with OAuth2 client credentials and lets admins and employees drive everyday RMM work in natural language — listing managed endpoints, checking patch compliance, deploying missing updates, installing software packages, running scripts, and rebooting devices — with policy guardrails, self-only constraints, and audit logging.

Book a Demo

What Dex does with Action1

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (CoAdmin)

List every organization, endpoint, and endpoint group in the Action1 tenant
Pull full endpoint details including hardware, OS, and patch/vulnerability status
Surface devices with missing critical updates or vulnerabilities across the fleet
List and inspect existing automation policies (patch schedules, maintenance windows)
Create new automation policies — patch deployment, software install, script execution, reboot
Browse the available software package catalog in Action1
Run reports and review patch compliance across the tenant

For employees (self-service)

Check whether your own computer has missing patches or pending updates
Deploy missing patches to your own device after approval
Install an approved software package onto your own computer
Uninstall software from your own device
Run a diagnostic or remediation script on your own computer
Reboot your own computer on demand

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Show me every managed endpoint missing a critical update and group them by organization
>Create a weekly patch deployment policy that pushes critical updates to "Finance-Laptops" every Sunday at 2 AM
>Which endpoints haven't reported in for more than 14 days?
>List every automation policy that targets the "Warehouse-PCs" group
>Deploy the latest Chrome package to all workstations in the "Sales" group

Employee prompts

>Am I missing any updates on my laptop?
>Install the missing security patches on my computer tonight
>Install Zoom on my computer
>My PC is sluggish — run the diagnostic script IT set up
>Reboot my computer now

Policy actions

Every action Dex can take on Action1 is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`action1_check_patch_status`	Check missing updates and patch compliance on the user's own endpoint	self-only
`action1_deploy_patches`	Deploy missing patches to the user's own endpoint	approvalself-only
`action1_install_software`	Install or uninstall software on the user's own endpoint	approvalself-only
`action1_run_script`	Run a diagnostic or remediation script on the user's own endpoint	approvalself-only
`action1_reboot_endpoint`	Reboot the user's own endpoint	approvalself-only

How to configure Action1

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
Sign in to Action1 as an administrator and go to Configuration > Users & API Credentials.
2
Create a new API credential for Dex and copy the Client ID (format `api-key-{uuid}@action1.com`) and Client Secret. The secret is shown once — store it immediately.
3
In Dex, enable the Action1 integration and paste both credentials.
4
Dex validates the credentials by running the OAuth2 client-credentials flow and a test call to `/organizations` before saving.
5
Configure policy actions (check_patch_status, deploy_patches, install_software, run_script, reboot_endpoint) with approval requirements and self-only constraints.

Vendor documentation ↗

Credentials required

client_id: Action1 API Client ID (from Configuration > Users & API Credentials). Format: api-key-{uuid}@action1.com
client_secret: Action1 API Client Secret (write-only — if lost, generate a new one in Configuration > Users & API Credentials)

Requirements

•Action1 tenant with at least one organization and managed endpoints enrolled
•API credentials created in Action1 Configuration > Users & API Credentials
•Every Action1 API call is scoped to an org_id — Dex resolves it automatically via /organizations
•OAuth2 tokens are refreshed automatically; a 401 response means the credentials need to be reconfigured
•All deploy, install, script, and reboot actions are modelled as Action1 automation policies under the hood

Related integrations

See Dex run Action1

Book a 30-minute walkthrough with our team and see how autonomous IT works in your environment — or get started for free.

Book a Demo Browse all integrations →