Integration reference

HTTP Trigger and Action reference

Call external HTTPS APIs from a FastHook Workflow with optional bearer, API key, or basic authentication.

Explore HTTP integrations →
0 Triggers1 ActionsManifests: Trigger v— · Action v1

Authentication

Choose no authentication or store reusable HTTP credentials in a connected FastHook account.

  • Action connection type: oauth2; available modes: None, Bearer Token, API Key, Basic Auth.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

The Trigger manifest does not declare a fixed base OAuth scope list. Installation access, API credentials, or the selected event configuration can still control available resources.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Trigger availability

The current manifest does not expose an available HTTP Trigger. Start the Workflow with another app, a schedule, or a Webhook Source, then use HTTP as an Action.

Use HTTP Actions

The current Action manifest contains 1 operations. Representative Actions include:

  • HTTP Request
View all 1 available Action definitions
ActionManifest keyAccess and authManifest rate limit
HTTP Requesthttp.requestNone declared
none · http_bearer · http_api_key · http_basic		60/minute

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

  1. Create a Source using another provider, a schedule, or an inbound Webhook.
  2. Create a Workflow with that Source as its Trigger.
  3. Add the required HTTP Action and select the connected account.
  4. Map Trigger or earlier-Step data into the Action fields with the field picker.
  5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
  6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in HTTP.

Troubleshooting HTTP

The account is missing or cannot be selected
Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.
A resource picker is empty
Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.
The editor asks for additional scopes
Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.
An active Workflow returns 401, 403, or a permission error
Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.
The provider returns 429 or a temporary 5xx
Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

  • Use allowlisted HTTPS endpoints and keep credentials in provider accounts instead of Workflow input fields.

Next