Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

PromptHub

Integrate with PromptHub projects, retrieve heads, and run prompts.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect PromptHub with Flows360

Integrate with PromptHub projects, retrieve heads, and run prompts.

Use the PromptHub connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and no declared triggers.

Available actions

  • List Projects
  • Get Project Head
  • Run Prompt
  • Get Current Account
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: PromptHub
  • Package: @activepieces/piece-prompthub@0.2.0
  • Exact artifact digest: sha256:317197858c7404b4838a885e1df7cda0c87dddcc3bd30d3e2dd19bc664430a2d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • List Projects (list_projects), List PromptHub projects for a team. Returns information about each project's head revision and groups. Classification: read.
  • Get Project Head (get_project_head), Get the production-ready version of a PromptHub project (typically the last commit on master/main branch). Useful for integrating prompts into your application. Classification: read.
  • Run Prompt (run_prompt), Run a PromptHub project with optional variables, branch/hash, and chat payload Classification: read.
  • Get Current Account (get_current_account), Get the authenticated PromptHub account associated with the API token, including its current team context. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects5
Supported actions5
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
List Projects Yes No List PromptHub projects for a team. Returns information about each project's head revision and groups.
Get Project Head Yes No Get the production-ready version of a PromptHub project (typically the last commit on master/main branch). Useful for integrating prompts into your application.
Run Prompt Yes No Run a PromptHub project with optional variables, branch/hash, and chat payload
Get Current Account Yes No Get the authenticated PromptHub account associated with the API token, including its current team context.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

List Projects · Read

List PromptHub projects for a team. Returns information about each project's head revision and groups.

list_projects · Risk: low · Retry: safe

Inputs

  • teamId · number · Required, The ID of the team. Can be found in your browser's URL bar when viewing Team Settings, or use current_team_id from /me endpoint.
  • group · string · Optional, Filter projects from a specific group. Must be URL-encoded if the group name contains spaces.
  • model · string · Optional, Filter projects where the head uses a specific model (e.g., gpt-4, claude-2, etc.).
  • provider · string · Optional, Filter projects where the head uses a specific model provider.
Get Project Head · Read

Get the production-ready version of a PromptHub project (typically the last commit on master/main branch). Useful for integrating prompts into your application.

get_project_head · Risk: low · Retry: safe

Inputs

  • projectId · number · Required, The ID of the project. Can be found in your browser's URL bar when viewing that project.
  • branch · string · Optional, Use the head of a specific branch. Defaults to your project's master/main branch. Must be URL-encoded if the branch name contains spaces or special characters.
  • fallback · boolean · Optional, When enabled, any placeholders not provided in variables will fall back to your Project/Team defaults. Your variable overrides always take precedence.
  • variables · object · Optional, Key-value pairs to override placeholders in the prompt. Both keys and values will be URL-encoded automatically.
Run Prompt · Read

Run a PromptHub project with optional variables, branch/hash, and chat payload

run_prompt · Risk: low · Retry: safe

Inputs

  • projectId · number · Required, The ID of the project to run.
  • branch · string · Optional, The branch name to run from (defaults to main/master).
  • hash · string · Optional, Specific commit hash to run from.
  • variables · object · Optional, Key-value pairs to pass as variables to the prompt.
  • messages · array · Optional, Chat messages for chat-based projects.
  • prompt · string · Optional, Override prompt text for the project.
  • metadata · object · Optional, Additional metadata to include with the run.
  • timeoutSeconds · number · Optional, Request timeout in seconds (max 600).
Get Current Account · Read

Get the authenticated PromptHub account associated with the API token, including its current team context.

get_current_account · Risk: low · Retry: safe

Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the PromptHub connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-prompthub@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required PromptHub connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-prompthub@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com