Overview

Pre-built tooling

Pre-built integrations

No pre-built integration yet (time to contribute: <48h)

Not seeing the integration you need? Build your own independently.

Access requirements

Pre-RequisitesStatusComment
Paid dev account
Paid test account
Partnership
App review
Security audit

Setup guide

No setup guide yet.

Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Contribute useful links by editing this page

API gotchas

  • The Microsoft Advertising API doesn’t offer a REST API, which means certain Nango functionalities won’t be accessible, including syncs, workflows, and proxy requests. To engage with the Microsoft Advertising API, developers must initially retrieve the access token utilizing the backend API. This token should then be utilized with official client libraries or a SOAP Client for further interaction.
  • If you are developing an app for users within your own organization and the app has already been granted adequate permissions at the organization level with user consent turned off, you must override the integration config when calling the create connect session method:
    • Override authorization_params by setting only scope: '.default' and "prompt": "" to remove the consent screen. Note that if consent is required it will prompt the user for consent due to the “.default” scope.
    • Override authorization_params by setting only scope: '.default offline_access' and "prompt": "" to remove the consent screen. Note that if consent is required it will prompt the user for consent due to the “.default” scope.
    • Set the .default scope documentation to ensure the permissions remain the same as those granted at the organization level.
const { data } = await nango.createConnectSession({
  end_user: {
    id: '<END-USER-ID>',
    email: '<END-USER-EMAIL>',
    display_name: '<END-USER-NAME>'
  },
  organization: {
    id: '<ORGANIZATION-ID>',
    display_name: '<ORGANIZATION-NAME>'
  },
  allowed_integrations: ['microsoft-ads'],
  integrations_config_defaults: {
    "microsoft-ads": {
      authorization_params: {
        scope: '.default offline_access',
        "prompt": ""
      }
    }
  }
});

If this is not done, the app will show a consent screen prompting the user to grant permissions which the user will be unable to do without admin access.

Add Getting Started links and Gotchas by editing this page