Google Application Integration errors
Common Google Cloud Application Integration errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 9
- Components
- 7
- Verified
- 9
- Official docs
- docs.cloud.google.com/application-integration/docs
9 errors in 7 groups
Application Integration setup1
Authentication profiles2
- PRINCIPAL needs roles/iam.serviceAccountUser to save this auth configThis Application Integration error means someone creates or edits a Service account or OIDC token authentication profile without permission to act as its service account. Grant the Service Account User role on the service account named in the profile to whoever manages the profile.
- PRINCIPAL needs roles/iam.serviceAccountUser to use auth configThis Application Integration error means the person publishing or testing, or the run that reaches the task, cannot act as the service account in the authentication profile. Grant the Service Account User role on the service account named in the profile.
Call Integration task1
Connector Event trigger1
Connector Event triggers1
Publishing and testing2
- Set a run-as service account. These triggers run with no callerThis Application Integration error means an integration created on or after October 15, 2026, with a trigger other than API or Private, has no run-as service account. Set a run-as service account on the integration.
- Your project requires a run-as service accountThis Application Integration error means a run without user credentials has no run-as service account, in a region where integration governance is enabled. Set a run-as service account on the integration before you publish or test.
Running integrations1
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.