Appbricx
Features

Build

  • Coding agents and MCP
  • UI components and hooks
  • Templates
  • Verify testing
  • Builder console

Data

  • Postgres database
  • Data API
  • Realtime

Users

  • Row-level security
  • Sign-in and auth
  • Organisations and teams
  • Payments

Logic

  • Workflows and jobs
  • Server functions and webhooks
  • AI in your app
  • Integrations

Ship and own

  • Backups and rollback
  • Hosting and domains
  • Self-host and export
All features
ShowcaseTemplatesIntegrationsPricingDocs
Log inStart free
  • Features
  • Showcase
  • Templates
  • Integrations
  • Pricing
  • Docs
  • Log in

Build

  • Coding agents and MCP
  • UI components and hooks
  • Templates
  • Verify testing
  • Builder console

Data

  • Postgres database
  • Data API
  • Realtime

Users

  • Row-level security
  • Sign-in and auth
  • Organisations and teams
  • Payments

Logic

  • Workflows and jobs
  • Server functions and webhooks
  • AI in your app
  • Integrations

Ship and own

  • Backups and rollback
  • Hosting and domains
  • Self-host and export
  1. Home
  2. Integrations
  3. Developer tools
  4. Custom API
{ }

Custom API

Connect any HTTPS API: store its base URL and auth header in the vault, then call it via the request action. Outbound calls are SSRF-guarded (https-only, public hosts only, no redirects). In Appbricx, your workflows and server functions call it by name once it is connected.

Connect Custom APIFull reference

What you can do

1 action, each one call from a workflow or a server function. Triggers come from your app: a row changing, a schedule or a webhook.

  • HTTP Requestrequest
    Call the connected API: props { method, path, body?, query? }. Path is resolved against the vaulted base URL; the vaulted secret is sent in the configured header.

Set it up

About two minutes, once per project or once for the whole workspace.

  1. Open Integrations in the builder

    Backend panel, Integrations tab, then Custom API. To connect it for every project, use Workspace settings, Integrations.

  2. Add your credentials

    Fill in the fields the provider needs (listed below). They are stored encrypted in the vault.

  3. Call an action

    From a workflow, by integration id and action name. The call answers with success, output and, when it fails, the reason.

    Workflow
    // .workflow.js (native ctx)
    export async function run(ctx) {
      const res = await ctx.integrations.invoke("custom_http", "request", {
        "method": "<method>",
        "path": "<path>"
      });
      if (!res.success) throw new Error(res.error);
      ctx.log.info("Custom API answered", { output: res.output });
    }

More in Developer tools

  • GitHub
  • GitLab
  • Bitly
  • Datadog
  • DigitalOcean
  • Figma
  • All of Developer tools
Category
Developer tools
Sign-in
Credentials
Actions
1
Integration id
custom_http
Maintained
Community package
Package
built in
Docs
Actions, inputs and examples

Custom API and its logo are trademarks of their owner, shown only to identify the service this integration connects to. Their use does not imply endorsement by, or affiliation with, that company.

Connect Custom API once. Every workflow can use it.

Start freeAll integrations
Appbricx

The backend, runtime and hosting for apps your coding agent builds. On our cloud, in yours, or on your own servers.

Features

Coding agents and MCPUI components and hooksTemplatesVerify testingBuilder consolePostgres databaseData APIRealtimeRow-level securitySign-in and authOrganisations and teamsPaymentsWorkflows and jobsServer functions and webhooksAI in your appIntegrationsBackups and rollbackHosting and domainsSelf-host and exportAll features

Product

ShowcaseTemplatesIntegrationsPricingFor coding agentsSelf-hostBring your own AI keyFAQ

Compare

Appbricx vs SupabaseLovable alternativeBolt alternativeFor freelancersFor agencies

Resources

DocumentationReferenceBlogSupportContact

© 2026 Appbricx. All rights reserved.

TermsPrivacyCookiesAcceptable Use