Skip to content

Action1

Connect Furl to Action1 using OAuth 2.0 with client credentials flow.

Action1 integration imports endpoint inventory and device state, allowing you to discover and monitor endpoints across your organization. Furl uses Action1 as a read-only data source — it does not push patches, run scripts, or take other actions in Action1.

  1. Log into Action1

    1. Go to https://app.action1.com
  2. Create API Credentials

    1. In the left-hand menu, click “Users & API Credentials”
    2. Under the API Access or Credentials section, click “Add Credentials” or “Create API Key”
    3. Fill out the new credential form:
      1. Name: e.g., Furl Endpoint Integration
      2. Assign a Role: Choose Enterprise Viewer
        • This role grants read-only access to endpoints and device data — appropriate for integrations
    4. After saving, a form will appear with:
      1. client_id
      2. client_secret
      3. 📋 Copy both immediately — the client_secret will not be shown again
  3. Find your Organization ID

    1. Go to the Action1 dashboard
    2. Look at the browser’s address bar:
    https://app.action1.com/dashboard?org=abc123xyz
    1. Copy the value after org= — this is your org_id
  4. Configure Action1 Integration in Furl

    1. Use the client_id, client_secret, and org_id to set up the Action1 integration in your Furl dashboard

Provide the following in Furl:

  • Organization ID - Your Action1 organization ID
  • Client ID - Your Action1 OAuth 2.0 client ID
  • Client Secret - Your Action1 OAuth 2.0 client secret
  • Get Endpoints → Retrieve all managed endpoints for the specified organization.
  • Query Devices → Query devices using filters (OS, status, group) to find specific endpoints. Supports limit and offset for pagination.
  • Get Installed Software → Retrieve software installed on a specific device by ID.
  • Ensure your OAuth credentials have the necessary permissions to access endpoint data. The Enterprise Viewer role provides the read-only access Furl needs.
  • Verify the Organization ID, Client ID, and Client Secret are correctly configured.