application-integration-authoring

Author, version, publish, and execute Google Cloud Application Integration workflows via REST API and Python client.

23.7k|2.0k|Updated Mar 31, 2026
Ready to run
npx skills add https://github.com/google/skills --skill application-integration-authoring-google
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: application-integration-authoring
Source: https://github.com/google/skills/tree/main/skills/cloud/application-integration-authoring
Command: npx skills add https://github.com/google/skills --skill application-integration-authoring-google

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing Application Integration workflows through manual console steps is slow and error-prone. This Skill automates the entire lifecycle: building integrations from JSON, versioning changes, publishing to environments, and invoking them programmatically—enabling CI/CD pipelines and infrastructure-as-code workflows. ## Core Features & Use Cases - Programmatic Authoring: Create and edit integration versions from JSON, upload them via REST API, and manage draft-to-active state transitions without the console. - Environment Promotion: Download a tested version, rewrite service account and config variables for the target environment, upload to the new project, and publish—all in one automated workflow. - Execution & Testing: Invoke published integrations synchronously (:execute) or asynchronously (:schedule), retrieve execution records and task state, and resolve suspended Approval or Suspend tasks via REST. - Use Case: A financial services team manages order-processing integrations across dev, staging, and production. They store integration JSON in Git, use Cloud Build to upload and publish versions on merge, and invoke integrations from microservices using the REST API—eliminating manual deployments and reducing rollout time from hours to minutes. ## Quick Start Download an integration version as JSON, modify the config variables and run-as service account for your target environment, then upload the updated JSON and publish it to make it live.

Frequently Asked Questions about application-integration-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload an integration version from JSON to Google Cloud?▼

Call `POST .../versions:upload` with a request body containing the JSON content and fileFormat set to "JSON". The endpoint creates the integration if it doesn't exist or adds a new DRAFT version if it does. The uploaded version remains in DRAFT state until you publish it.

How do I promote an integration across projects?▼

Download the version from the source project using `versions:download`, rewrite the runAsServiceAccount to match the target project's service account, upload the modified JSON to the target project, and publish it with environment-specific configParameters. Unknown keys in configParameters are silently ignored, so keys must exactly match integrationConfigParameters keys including backticks.

What's the difference between config variables and authentication profiles?▼

Config variables store non-secret environment values (URLs, topic names) and are exported in plain text. Authentication profiles (authConfigs) store API keys, OAuth credentials, and certificates—they are regional, not included in downloaded files, and must be created separately in each target project.

Can I test an integration before publishing to production?▼

Yes. Publish the version to a non-production project and invoke it there using `integrations:execute`. Do not use the deprecated `integrations:test` endpoint because it requires an undocumented clientId parameter. Draft testing also cannot run Approval, Suspend, or Timer tasks.

How do I invoke a published integration programmatically?▼

Call `POST .../integrations/INTEGRATION_NAME:execute` (synchronous, max 2 minutes) or `:schedule` (asynchronous) with triggerId set to your API trigger name (e.g., "api_trigger/order_webhook") and inputParameters as JSON. Read executionId and outputParameters from the response.

What IAM roles do I need to upload and publish integrations?▼

Upload requires roles/integrations.integrationEditor (which includes integrations.integrationVersions.create). Publish requires roles/integrations.integrationDeployer or roles/integrations.integrationEditor, plus roles/iam.serviceAccountUser on the integration's runAsServiceAccount when one is set.