Combine políticas e recursos em um fluxo compartilhado que você possa consumir a partir de vários proxies de API e até mesmo de outros fluxos compartilhados. Ele é semelhante a um proxy, mas um fluxo compartilhado não tem endpoint. É possível usá-lo somente a partir de um proxy de API ou fluxo compartilhado que esteja na mesma organização do fluxo compartilhado.
Para criar um fluxo compartilhado usando a Apigee no Cloud Code:
Realize uma das seguintes etapas:
Posicione o cursor sobre a pasta sharedflows no seu espaço de trabalho local e clique em
.
Selecione Visualizar > Paleta de Comandos para abrir a paleta de comandos e selecione Cloud Code: criar pacote de fluxo compartilhado da Apigee.
O assistente "Criar fluxo compartilhado" é aberto.
Digite um nome exclusivo para o fluxo compartilhado no prompt e aperte Enter.
Depois de concluir as etapas no assistente, o novo nome do fluxo compartilhado vai aparecer
em sharedflows na seção "Apigee". Cada pasta de fluxo compartilhado é estruturada conforme descrito em Estrutura do diretório do pacote de fluxo compartilhado
Como fazer upload de um pacote de fluxo compartilhado
Para fazer upload de um pacote de fluxo compartilhado usando a Apigee no Cloud Code:
Realize uma das seguintes ações:
No seu espaço de trabalho local, posicione o cursor sobre a pasta sharedflows e clique em .
Selecione Visualizar > Paleta de comandos para abrir a paleta de comandos e selecione Cloud Code: importar pacote de fluxo compartilhado da Apigee.
Acesse o pacote de fluxo compartilhado que será feito upload e clique em Importar fluxo compartilhado.
O pacote de fluxo compartilhado precisa ser estruturado conforme descrito em Estrutura do diretório do pacote de fluxo compartilhado.
(Opcional) Por padrão, o nome do arquivo ZIP menos a extensão dele é usado para o nome do fluxo compartilhado. Se o nome não for exclusivo, você deverá digitar um nome exclusivo.
A pasta de fluxo compartilhado enviada é adicionada em sharedflows no seu espaço de trabalho do Apigee.
Como configurar fluxos compartilhados
Configure fluxos compartilhados conforme descrito nos seguintes tópicos:
Você pode chamar um fluxo compartilhado usando a política FlowCallout, conforme descrito em Política FlowCallout.
Além disso, ao anexar um fluxo compartilhado a um gancho de fluxo, é possível executá-lo antes de um proxy ou de uma solicitação de destino, ou depois de um proxy ou uma resposta de destino. Veja mais informações em:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-05 UTC."],[[["\u003cp\u003eThis page covers creating and managing shared flows in Apigee and Apigee hybrid, which are reusable sequences of policies and resources.\u003c/p\u003e\n"],["\u003cp\u003eShared flows are similar to API proxies but lack endpoints, and they are called from API proxies or other shared flows within the same organization.\u003c/p\u003e\n"],["\u003cp\u003eYou can create a new shared flow using Apigee in Cloud Code by using a wizard or command, which involves specifying a unique name.\u003c/p\u003e\n"],["\u003cp\u003eShared flow bundles can be imported into Apigee in Cloud Code, and you can configure shared flows by creating reusable ones, adding policies and managing resources.\u003c/p\u003e\n"],["\u003cp\u003eShared flows can be called via the FlowCallout policy or by attaching them to flow hooks, allowing execution before or after proxy or target requests/responses, but runtime dependency validation is necessary.\u003c/p\u003e\n"]]],[],null,["# Developing shared flows\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n\u003cbr /\u003e\n\nCombine policies and resources into a shared flow that you can consume from multiple API proxies, and even from other shared flows. Although it's like a proxy, a shared flow has no endpoint. It can be used only from an API proxy or shared flow that's in the same organization as the shared flow itself.\n\nDevelop your shared flows using Apigee in Cloud Code as described in the following sections. See also [Managing folders and files in an Apigee workspace](/apigee/docs/api-platform/local-development/vscode/manage-apigee-workspace#manage-folders-files).\n| **Before you begin** : Familiarize yourself with the concepts described in the following topics:\n|\n| - [Creating reusable shared flows](/apigee/docs/api-platform/fundamentals/shared-flows)\n| - [Attaching a shared flow using a flow hook](/apigee/docs/api-platform/fundamentals/flow-hooks)\n\nCreating a shared flow\n----------------------\n\nTo create a shared flow using Apigee in Cloud Code:\n\n1. Perform one of the following steps:\n\n - Position your cursor over the **sharedflows** folder in your local\n workspace and click\n .\n\n - Select **View \\\u003e Command Palette** to open the Command palette and select **Cloud Code: Create Apigee shared flow bundle**.\n\n The Create shared flow wizard opens.\n2. Enter a unique name for the shared flow at the prompt and press \u003ckbd\u003eEnter\u003c/kbd\u003e.\n\nAfter you complete the steps in the wizard, the new shared flow name appears\nunder **sharedflows** in the Apigee section. Each shared flow folder is structured as described in [Shared flow bundle directory structure](/apigee/docs/api-platform/reference/shared-flow-bundle-configuration-reference#sharedflowbundlestructure)\n\nUploading a shared flow bundle\n------------------------------\n\nTo upload a shared flow bundle using Apigee in Cloud Code:\n\n1. Perform one of the following actions:\n\n - In your local workspace, position your cursor over the **sharedflows** folder and click .\n\n - Select **View \\\u003e Command Palette** to open the Command palette and select **Cloud Code: Import Apigee shared flow bundle**.\n\n2. Navigate to the shared flow bundle that you want to upload and click **Import shared flow** .\n The shared flow bundle must be structured as described in [Shared flow bundle directory structure](/apigee/docs/api-platform/reference/shared-flow-bundle-configuration-reference#sharedflowbundlestructure).\n\n3. (Optional) By default, the name of the zip file minus its extension is used for the name of the shared flow. If this name is not unique, you are prompted to enter a unique name.\n\nThe uploaded shared flow folder is added under **sharedflows** in your Apigee workspace.\n\nConfiguring shared flows\n------------------------\n\nConfigure shared flows as described in the following topics:\n\n- [Creating reusable shared flows](/apigee/docs/api-platform/fundamentals/shared-flows)\n- [Adding features using policies](/apigee/docs/api-platform/local-development/vscode/manage-policies)\n- [Managing resources](/apigee/docs/api-platform/local-development/vscode/manage-resources)\n\nUsing shared flows\n------------------\n\nYou can call a shared flow using the FlowCallout policy, as described in [FlowCallout policy](/apigee/docs/api-platform/reference/policies/flow-callout-policy).\n\nIn addition, by attaching a shared flow to a flow hook you can execute the shared flow before a proxy or target request, or after a proxy or target response. For more information, see:\n\n- [Attaching a shared flow using a flow hook](/apigee/docs/api-platform/fundamentals/flow-hooks) (conceptual overview)\n- [Attaching shared flows using flow hooks (flowhooks.json)](/apigee/docs/api-platform/local-development/vscode/deploy-environment#attaching_shared_flows_using_flow_hooks_flowhooksjson) (steps using Apigee in Cloud Code)\n\n\u003cbr /\u003e\n\n| **Note:** Apigee does not validate the dependencies between shared flows and API proxies at deploy time. For example, if the FlowCallout policy in an API proxy references a shared flow that either doesn't exist or isn't deployed, API proxy deployment still succeeds. When Apigee checks the dependency at runtime and validation fails, Apigee throws an API proxy error with a `500` HTTP status code."]]
.
.