REFERENCE / META
Access / 25 min

Create a Meta app and get tokens

Create the app, choose permissions, test a token, and plan how it will stay valid.

What you are making

The app identifies your integration. A token proves who is using it. Permissions limit what that token can do.

1Create app
2Add access
3Make token
4Test it

Create the app

  1. Open Meta for Developers → My Apps → Create App.
  2. Choose the business use case that includes the Marketing API. Meta changes these labels occasionally, so follow the use case rather than an old screenshot.
  3. Connect the app to the Business Portfolio that owns the assets you need.
  4. Add the Marketing API product or use case when Meta asks which APIs the app will use.

Choose permissions

  • Use ads_read for reporting and reading ad-account data.
  • Use ads_management only when the automation must create or change campaigns, ad sets, ads, or audiences.
  • Add business_management only when the job truly needs Business Portfolio assets.

Start small. A token cannot use a permission your app, user, and business assets do not all allow.

Token life

A short-lived user token is useful for a quick test. A long-lived user token lasts longer but still needs renewal planning. For a server automation owned by a business, a System User token is often easier to operate because access is managed inside Business Settings.

If you exchange a user token for a longer-lived one, do it on a server. The exchange uses the app secret, which must never be placed in browser code, screenshots, workflow downloads, or public URLs.

Test the token

Use Meta’s Access Token Debugger to check the app, user, expiry, and granted permissions. Then make one read-only request for the connected ad account before building anything that writes data.

Keep it safe

  • Store tokens in n8n credentials or environment variables.
  • Do not paste tokens directly into node URLs or Code steps.
  • Rotate a token when someone loses access, a secret may have leaked, or the automation changes owner.
  • App Review and business verification may be required before people outside the app’s roles can use advanced permissions.

Official references: Meta app development, Marketing API authorization, and access tokens.