Google Application Integration · Running integrations

PRINCIPAL needs roles/iam.serviceAccountUser to run this integration

Short answer

This Application Integration error means the person, automation or trigger that starts an integration cannot act as its run-as service account. Grant the Service Account User role to whoever starts the integration. For a trigger, that is the trigger's service account.

VerifiedLast verified

01Error text

Google Application Integration error
PRINCIPAL needs roles/iam.serviceAccountUser on SERVICE_ACCOUNT (or its project) to run this integration.

02Likely causes

  • A person, automation or trigger starts an integration but can't act as its run-as service account.
  • In a Call Integration task, the caller or the calling integration's run-as service account can't act as the sub-integration's run-as service account.

03How to fix it

  1. Grant the Service Account User role to whoever starts the integration. For a trigger, that is the trigger's service account.

iNotes

An API call returns the error and nothing appears in execution logs. A Cloud Scheduler job reports a PERMISSION_DENIED error.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.