passthrough-api_skill

This skill executes actions across connected platforms via the Passthrough API, enabling rapid automation and data operations from a unified interface.

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill picahq/skills --skill passthrough-api

  • SKILL.md14.1 KB

Overview

This skill executes HTTP requests across 200+ platforms using Pica's unified Passthrough API. It lets you discover connectors and actions, manage user connections, and forward requests to third‑party APIs through a single secure endpoint. Ideal for server-side automation, integration platforms, and developer tools.

How this skill works

The skill calls Pica's REST endpoints at https://api.picaos.com using an x-pica-secret API key and, for passthrough calls, an x-pica-connection-key to select the user connection. It can list available connectors and actions, fetch action schemas (knowledge), manage vault connections, and proxy arbitrary HTTP requests to the upstream platform via /v1/passthrough/{path}. Responses mirror the underlying platform's API.

When to use it

  • Send or receive data to/from third‑party platforms without implementing each provider's auth.
  • Build integrations that must target many platforms (Gmail, Slack, HubSpot, Stripe, etc.).
  • Centralize connection management and reuse stored credentials across environments.
  • Prototype multi‑platform workflows quickly in sandbox before switching to production.
  • Execute platform-specific HTTP actions while preserving native response formats.

Best practices

  • Store and rotate x-pica-secret keys securely and keep sandbox/production keys separate.
  • List and validate available-actions and action knowledge before sending passthrough requests to ensure required fields are present.
  • Use connection listing endpoints to retrieve valid x-pica-connection-key values instead of hardcoding connection keys.
  • Implement exponential backoff and retry logic for 429 rate limits and transient 5xx errors.
  • Scope requests by identity and identityType for multi‑tenant environments to avoid cross-tenant access.

Example use cases

  • Send transactional emails via Gmail by calling the passthrough send endpoint with a stored Gmail connection key.
  • Post messages to Slack channels from an automation workflow using the Slack chat.postMessage passthrough path.
  • Create HubSpot contacts or update CRM objects through the passthrough CRM endpoints.
  • Fetch Stripe customers or invoices via passthrough queries for billing reconciliation.
  • Build a single integration layer in your app that routes requests to many providers without custom OAuth code per provider.

FAQ

Include x-pica-secret (API key) and x-pica-connection-key (the connection identifier). Content-Type is required for JSON bodies.

How do I discover required parameters for an action?

Call GET /v1/actions/{actionId}/knowledge to retrieve the action schema, body properties, and required fields.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational