Skip to main content
HTTP-based connections let Planasonix pull from vendor APIs, call AI endpoints with structured prompts, query GraphQL services, and integrate with SAP landscapes. Webhook connections let external systems push payloads into Planasonix when you expose a secured ingress URL.

​
Connection types

​
OpenAPI and Swagger import

When a vendor publishes OpenAPI 2.x (Swagger) or OpenAPI 3.x, you can import the spec to accelerate setup:
  • Operations become selectable endpoints with method, path, and documented parameters.
  • Security schemes in the spec map to credential types where Planasonix supports them (API key headers, OAuth2 flows, basic auth).
  • Models help pre-fill response parsing when the connector generates suggested field mappings.
After import, review servers and base URLs for environment accuracy (production vs sandbox). Specs sometimes embed example hosts that you must override on the connection.
Pin imports to a version-controlled copy of the OpenAPI file in your repository rather than a moving URL, so pipeline behavior does not change when the vendor publishes a breaking spec update without notice.

​
Endpoint discovery and parameter configuration

1

Choose base URL and default headers

Set the scheme, host, and optional global headers (for example Accept: application/json or a required X-API-Version). Store secrets in credentials, not as static header values in shared connections.
2

Discover or define operations

If you imported OpenAPI, pick the operation from the catalog. Otherwise, define the path template, HTTP method, query parameters, and body schema manually to match the vendor’s documentation.
3

Configure pagination and rate limits

Map cursor, offset, or link-header pagination patterns so Planasonix can walk large result sets. Set backoff and concurrency to stay inside vendor quotas and your own SLOs.
4

Map responses to tabular or document shape

Choose JSONPath or equivalent extraction rules so nested payloads flatten into columns or variant structures your downstream warehouse expects.
5

Test with recorded fixtures in lower environments

Run sample calls against sandbox keys, capture status codes and error bodies, and adjust retry rules for idempotent GET vs non-idempotent POST behavior.

​
Webhook security

For inbound webhooks, configure HMAC signature verification or mTLS when the sender supports it. Rotate shared secrets on the same schedule as API keys. Reject requests that lack required headers or fall outside allowed source IP ranges if your gateway enforces network rules.
Do not log full webhook payloads at INFO if they contain PII or payment data. Use structured logging with field redaction and retain raw bodies only in approved secure storage if compliance requires it.

SaaS applications

Curated connectors with OAuth and object metadata when a packaged connector exists.

AI providers

First-class OpenAI, Anthropic, and Google AI connections for transforms and Copilot.

Credentials management

API keys, OAuth clients, and basic auth material for HTTP connections.

Orchestration webhooks

Outbound notifications and pipeline triggers from Planasonix.