Combina políticas y recursos en un flujo compartido que puedes consumir desde varios proxies de API, y también desde otros flujos de uso compartido. Aunque es como un proxy, un flujo compartido no tiene extremo. Solo se puede usar desde un proxy de API o un flujo compartido que se encuentre en la misma organización que el flujo compartido en sí.
Para crear un flujo compartido mediante Apigee en Cloud Code, haz lo siguiente:
Realiza uno de los siguientes pasos:
Coloca el cursor sobre la carpeta sharedflows en tu espacio de trabajo local y haz clic en .
Selecciona View > Command pal para abrir la paleta de comandos y selecciona Cloud Code: Create Apigee shared flow bundle.
Se abrirá el asistente para crear un flujo compartido.
Ingresa un nombre único para el flujo compartido en el mensaje y presiona Intro.
Después de completar los pasos del asistente, el nuevo nombre del flujo compartido aparecerá en sharedflows en la sección Apigee. Cada carpeta de flujo compartido está estructurada como se describe en la estructura del directorio del paquete de flujo compartido.
Sube un paquete de flujo compartido
Para subir un paquete de flujo compartido con Apigee en Cloud Code, haz lo siguiente:
Realiza una de las siguientes acciones:
En tu espacio de trabajo local, coloca el cursor sobre la carpeta sharedflows y haz clic en .
Selecciona View > Command pal para abrir la paleta de comandos y selecciona Cloud Code: Import Apigee shared flow bundle.
Navega hasta el paquete de flujo compartido que deseas subir y haz clic en Import shared flow.
El paquete de flujo compartido debe estar estructurado como se describe en la estructura del directorio del paquete de flujo compartido.
De forma predeterminada, se usa el nombre del archivo ZIP menos su extensión para el nombre del flujo compartido (opcional). Si este nombre no es único, se te pedirá que ingreses un nombre único.
La carpeta de flujo compartido que se subió se agrega en sharedflows en tu espacio de trabajo de Apigee.
Configura flujos compartidos
Configura los flujos compartidos como se describe en los siguientes temas:
Puedes llamar a un flujo compartido con la política FlowCallout, como se describe en la política FlowCallout.
Además, si adjuntas un flujo compartido a un hook de flujo, puedes ejecutar el flujo compartido antes de una solicitud de destino o proxy, o después de una respuesta de proxy o destino. Para obtener más información, consulta:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 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."]]
.
.