> ## Documentation Index > Fetch the complete documentation index at: https://docs.letsflow.ai/llms.txt > Use this file to discover all available pages before exploring further. # Addigy > Manage Apple devices, policies, and compliance through Addigy automations. export const flowWebUrl = "https://app.letsflow.ai"; Flow uses this integration to run Addigy actions from automations with the team connection selected during setup. Admins choose which actions that team can use, and automation runs call only those allowed actions through the connection. ### Prepare in Addigy Your Addigy account needs **View Integrations API Keys** and **Create Integrations API Keys** permissions to create a token. 1. In Addigy, open **Account > Integrations > API & Webhooks**. 2. In the **Addigy API** section, choose **New API Token**. 3. Give the token permission to view policies so Flow can validate the connection. 4. Add the permissions needed by your intended automation actions. 5. Copy the token when Addigy displays it. Addigy does not display the token again. Use an API v2 token. API v1 client IDs and client secrets are no longer supported. See [Addigy API v2 setup](https://support.addigy.com/hc/en-us/articles/16938210315411-API-Documentation-v2) for token permissions and creation steps. ### Connect in Flow 1. Open **Integrations**. 2. Choose **Add connection**. 3. Search for **Addigy**. 4. Select the **Addigy** card. Open Flow 1. Choose who can use the connection. 2. Select **Continue** through the setup steps. 3. Give the connection a name. 4. Select **Connect** to open the credential form. 5. Enter your Addigy API v2 token. 6. Submit the form. 7. Wait for Flow to validate the connection. 8. Open the new connection's **Automations** tab. 9. Choose **Enable** for the intended team or teams. 10. Select the Addigy actions automations can run. 11. Choose **Save** if you changed the selection. ### Troubleshooting | Problem | Action | | - | - | | Flow rejects the token. | Create a new API v2 token in Addigy and reconnect in Flow. | | Flow reports missing permission to view policies. | Create an API v2 token with permission to view policies and reconnect in Flow. | | An automation action reports missing permissions. | Create a token with permission for that action and reconnect in Flow. Confirm that the team allows the action in Flow. | | The connection exists, but the team cannot run actions. | Open the connection's **Automations** tab and enable it for the team. | | Addigy is temporarily unavailable or limits requests. | Wait before you retry. See [Addigy API limits](https://support.addigy.com/hc/en-us/articles/16938210315411-API-Documentation-v2) for the rate limit and rejection period. | ## Permissions and scopes This integration does not define provider scopes. ## Supported actions | Action | Description | Risk | | - | - | - | | Add organization note to ticket. | Add an organization note documenting investigation, actions, or resolution on a ticket. | high | | Assigns policies to an MDM configuration profile | Assign an MDM configuration profile to policies for scalable configuration enforcement. | high | | Close device ticket. | Close an Addigy device ticket after remediation and verification. | high | | Create a policy. | Create a core Addigy policy used to manage device groups and assigned assets. | high | | Deploy profile to list of devices | Deploy an MDM profile directly to selected devices for targeted remediation or urgent configuration. | high | | Device Policy Assignment | Assign devices to an Addigy policy for configuration, software, and monitoring rollout. | high | | Device Policy Unassignment | Remove devices from an incorrect or obsolete policy; requires approval because management coverage can be removed. | high | | Disable Lost Mode | Disable Lost Mode after device recovery; requires approval and incident verification. | high | | Enable Lost Mode | Enable Lost Mode to protect a missing managed device; disruptive and requires approval. | high | | Erases an MDM device | Remotely erase a compromised or retired MDM device; irreversible and requires explicit approval. | high | | Get command output. | Retrieve command output to verify the result of a remediation run on a device. | low | | Get device tickets. | Retrieve tickets associated with a device for incident context and workflow correlation. | low | | Get MDM Device Details | Verify detailed MDM state for a device before and after administrative actions. | low | | Get Policy Info | Search policies to resolve policy IDs and verify targets before assignment or modification. | low | | Get received alerts matching a filter. | Filter received Addigy alerts to identify incidents requiring triage or remediation. | low | | Gets available updates reported for multiple devices | Query available system updates across devices to identify patching targets. | low | | Gets MDM configuration profiles | List MDM configuration profiles to locate valid profiles before assignment or deployment. | low | | Lock mdm device | Remotely lock a managed device during loss or security incidents; disruptive and requires approval. | high | | Perform an action on received alerts, such as muting, acknowledging or resolving them. | Acknowledge, mute, or resolve received alerts after ITSM handling and remediation. | high | | Removes a device | Deprovision a retired or invalid device from Addigy; destructive and requires explicit approval. | high | | Requests to schedule system updates (on-demand) for devices via MDM command. | Trigger on-demand system updates for selected devices; requires approval because it may disrupt users. | high | | Run devices command. | Run an Addigy command across selected devices for scripted diagnosis or remediation. | high | | Universal Search Devices | Canonical organization-scoped universal search for locating managed devices in Addigy workflows. | low | | Update a policy. | Update policy configuration as part of standard administrative change workflows. | high | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.