Google Application Integration · Call Integration task
Integration needs a run-as service account to run asynchronously
Short answer
This Application Integration error means a sub-integration is called asynchronously and has no run-as service account, even if the calling integration has one. Set a run-as service account on the sub-integration, or call it synchronously.
VerifiedLast verified
01Error text
Integration NAME needs a run-as service account to run asynchronously via trigger TRIGGER_ID.02Likely causes
- The sub-integration is called asynchronously and has no run-as service account.
03How to fix it
- Set a run-as service account on the sub-integration, or call it synchronously.
- Grant the Service Account User role on the sub-integration's run-as service account.
04Official documentation
→Related errors
- PRINCIPAL needs roles/iam.serviceAccountUser to run this integrationThis 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.
- 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.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.