In some cases, you may need to create multiple GCP projects to use Dialogflow:
- You may find it useful to create one project for authentication/quotas/billing and additional projects for agent data.
- Each project can have at most one agent per region, so you need multiple projects if you need multiple agents in the same region.
When you make calls to the API, you typically provide service account keys for authentication. Each service account is owned by a specific project, but service accounts may be provided roles to access resources for other projects. The project associated with the service account you provide for an API call is referred to as the consumer project.
The following are determined by your consumer project for an API call:
- Charges for the API call.
- Quota constraints.
- The Dialogflow edition for the API call. If your consumer project does not have an agent, you should create an empty agent in order to choose an edition.
When you make calls to the API, your request specifies the agent's project. This project is referred to as the resource project.
The following is determined by your resource project for an API call:
- All agent data except edition.