OAuth or Personal Access Token for Make - which should I use

[ScottWorld]

@MLO

Is this possible with 3rd-party integrations or is everything tied to a key tied to an individual account? (I thought OAuth solved this but reading another thread on OAuth, it appears it doesn’t?)

[We recently upgraded to Enterprise, if that makes a difference, which I had assumed it would, but I can’t figure that out either.]

Unfortunately, everything is always tied to an individual account.

However, since you are on the Enterprise plan, you can create free service accounts which:

(a) are only used for API access,
(b) won’t cost you any additional money, and
(c) won’t get affected when people leave the organization.

I talk more about these free service accounts in this thread:

Enterprise customers can create free service accounts for API access

I recently discovered that Enterprise customers can create free “service accounts” for API access to Airtable. These are not “user accounts” that can log into Airtable’s website, but they are “API-only accounts” that can only access Airtable’s API via a personal access token or by authorizing an OAuth integration. The advantage is that this service account does not count towards the user count for billing purposes. So, for all intents and purposes, this is a “free account”. More details here: …

@MLO

(I got stuck on the request to enter a url link and couldn’t find more information.)

The app that you are connecting to would need to provide you with this URL.

For example, for Make.com, the URL is https://www.integromat.com/oauth/cb/airtable3

From what I understand, I believe this means that each oAuth integration can only be used with one external app, whereas a Personal Access Token can be used across multiple apps.