Skip to content
AutomatedOn Help Centre

Connect Aptem, Microsoft Dynamics 365 or Dataverse

Updated 19 October 2026 · For back office users

Aptem and Microsoft Dynamics 365 (Dataverse) both have OData APIs, so you connect them with an ordinary OData Data Source. There's no separate connector to switch on.

Before you start

You'll need someone who administers the other system to give you the API address and the right credentials. AutomatedOn only reads what those credentials are allowed to see.

Steps

  1. Get the API details

    • Aptem: ask your Aptem administrator or Aptem for your tenant's OData API address and an API token, and which header the token should be sent in.
    • Dynamics 365 / Dataverse: your Microsoft administrator registers an application for AutomatedOn and gives it access to your environment. You'll need the environment's Web API address (it usually ends in /api/data/v9.2), the tenant's token endpoint, the scope for your environment, and the application's client ID and secret.

  2. Create the API Auth Profile

    • Aptem: choose ApiKey. If you leave Header Name empty, the token is sent in a header called x-api-token. Set Header Name if Aptem tells you to use a different header.
    • Dynamics 365 / Dataverse: choose ClientCredentials. Set Token Endpoint to your tenant's token URL, typically https://login.microsoftonline.com/your-tenant-id/oauth2/v2.0/token, and Scope to your environment address followed by /.default.

    Enter a readable Credential Key in both cases, save and publish.

  3. Ask Three 17 to add the secret

    Contact Three 17 support with the Credential Key. For Aptem they'll store the token; for Dynamics they'll store the client ID and client secret.

  4. Create the OData data source

    Create a Data Source in the Data Sources folder, enter the API address in OData Endpoint, and pick the profile. Save, publish and select Test Connection.

  5. Check you can see data

    Create a Dataset under the data source. If the Entity Set list fills with names (for example contacts in Dataverse), the connection works. Pick fields and use the Preview tab to see real records.

More detail

Tips for these systems

  • Field lists come straight from the system's own description of its data, including fields added by your organisation.
  • Dataverse uses lower-case entity set names, usually plural, such as contacts and opportunities.
  • Rules that look up extra fields for each record can ask for a long list of fields. AutomatedOn splits very long field lists across several requests automatically, so the request isn't rejected for being too long.

Was this guide helpful?