Back to Learn

Aptabit Platformv3.7

Modules

Integrations

Connections to external systems, more than 99 ready-made connectors, authentication, and outbound protection.

On this page

Integrations connect the Aptabit Platform to your organization's and your partners' systems. Each connection is registered once, with its resources and credentials, and reused by flows.

Connections

In Integrations, register one connection per system. Available types:

Type Use in flows
REST API Executed by the integration block.
GraphQL Executed by the integration block, over HTTP.
Webhook An HTTP call to a receiving URL of the target system, made by the integration block when the flow reaches it.
Database Registration and connectivity test.
Message queue Registration and connectivity test.
File transfer Registration and connectivity test.
gRPC and WebSocket Registration and connectivity test.
Other Free-form registration.

Each connection lists named resources (routes, with method and sample payload) and offers a connection test. For databases, the test validates sign-in and a query on PostgreSQL and a TCP connection on the others; for queues, Redis answers a PING and the others get a TCP test; for SFTP, the test reads the SSH server's banner.

Flows execute only HTTP connections: REST API, GraphQL, and Webhook (a call made by the flow, not an automatic delivery of platform events). Database, queue, file transfer, gRPC, and WebSocket connections are registered and checked, but flows do not execute them. For data from databases and spreadsheets, use the data contexts in Storage.

Authentication

Method Detail
None For public APIs or APIs protected by the network.
API key Sent in a header.
Bearer A fixed token in the Authorization header.
Basic User name and password.
OAuth 2.0 client credentials Token obtained and cached by the platform.
OAuth 2.0 refresh token Automatic renewal; the new refresh token is saved before use.

Some integration templates have vendor-specific signing, such as TikTok Shop's HMAC-SHA256 signature, Veeam sessions, and HPE OpsRamp OAuth.

Credentials are encrypted in the database (XChaCha20-Poly1305), decrypted only at call time, and never reach the browser.

Integration templates

The catalog offers more than 99 ready-made connectors. Examples by category:

Category Systems
E-commerce Amazon Selling Partner, Mercado Livre, Shopify, Meta Product Catalog, and TikTok Shop.
Messaging WhatsApp Cloud API, Telegram Bot API, Twilio, and Slack.
Productivity Microsoft 365 (Graph) and Google Workspace.
ERP TOTVS Protheus.
CRM Salesforce.
DevOps Atlassian Jira and Confluence.
ITOM HPE OpsRamp.
Backup Veeam Enterprise Manager.
Security Netskope.
Market data AwesomeAPI Economia.
Database SAP HANA (registration and connectivity test).

An integration template fills in the base URL, the authentication, and the most used resources. You provide the credentials and adjust what you need. Systems outside the catalog are registered as custom connections.

Use in flows

  1. Register the connection and run the test.
  2. In the flow, add an Integration block and choose the connection and the resource.
  3. Map the previous step's fields to the request body.
  4. Use the response in the following blocks, for example in a Decision or Data write block.

Systems and devices connected through APIs take part in flows the same way.

Outbound protection

Every URL a user can influence (connections, provider URLs, and inference servers) goes through SSRF protection:

  • Private, loopback, link-local, CGNAT, and cloud metadata addresses are blocked by default.
  • Integration calls do not follow redirects.
  • Internal hosts the installation needs to reach, such as a system on the corporate network, are allowed explicitly in the API's APTABIT_SSRF_ALLOWED_HOSTS variable, separated by commas.

Planned capabilities

Planned: MCP (Model Context Protocol) servers, containerized scripts, and platform event webhooks with HMAC signatures. Today, inbound calls into a flow go through the flow endpoint.

Documentationv3.7