third-party-integrations

Document integration patterns for external services using cloud function proxies.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/trusted-american/marketplace --skill third-party-integrations-trusted-american
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: third-party-integrations
Source: https://github.com/trusted-american/marketplace/tree/main/plugins/a3-plugin/skills/third-party-integrations
Command: npx skills add https://github.com/trusted-american/marketplace --skill third-party-integrations-trusted-american

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes patterns and architectures for connecting A3 to external services, reducing duplication and accelerating integration work.

Core Features & Use Cases

  • Integration Architecture: Frontend Component → REST Adapter (adapter/firebase.ts) → Cloud Function HTTPS Endpoint → Third-Party API, with server-side keys and secure handling.
  • Service coverage: Stripe, Mailgun, PandaDoc, Algolia, HubSpot, Salesforce, OpenAI, Intercom, Sentry, Google Maps, Vimeo, and other providers.
  • Real-world use case: Rapidly prototype and standardize new service adapters by following the documented pattern and reusable components.

Quick Start

Implement a new service adapter by following the Frontend Component → REST Adapter → Cloud Function pattern described above to connect the service.

Frequently Asked Questions about third-party-integrations

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

FAQPage Schema
How do I build a third-party API integration that keeps server-side keys secure?

Secure third-party API integration uses a Frontend Component → REST Adapter → Cloud Function HTTPS Endpoint pattern. This routes external service requests through cloud functions, keeping server-side keys secure and handling sensitive data safely.

What is the standard architecture pattern for connecting to external services like Stripe and OpenAI?

The standard external service architecture pattern connects a frontend component to a REST adapter, which calls a cloud function proxy. This unifies integration patterns for providers like Stripe and OpenAI, reducing architectural duplication across your codebase.

Can I use this integration pattern to connect to services like HubSpot, Salesforce, and Mailgun?

Yes, this integration pattern supports connecting to HubSpot, Salesforce, and Mailgun. It provides reusable adapters and standardized architecture guidance for these external services, allowing you to rapidly prototype new service connections.

How do I rapidly prototype and standardize a new service adapter for a third-party platform?

To prototype a new service adapter, follow the documented frontend component to REST adapter to cloud function pattern. This standardizes third-party platform connections by leveraging reusable components and consistent architecture guidance.

Does this pattern work for frontend-backend integrations with Google Maps and Vimeo?

Yes, the pattern works for frontend-backend integrations with Google Maps and Vimeo. It applies a cloud function proxy pattern to standardize external service connections, ensuring consistent architecture across all supported providers.

What's the best way to manage multiple external service integrations without duplicating code?

The best way to manage multiple external service integrations without duplicating code is using a centralized REST adapter pattern. It routes requests through cloud function HTTPS endpoints, standardizing architecture and creating reusable components for all providers.