Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Fountain

Automate your complete HR hiring and onboarding workflow. Manage applicants, job openings, interview scheduling, and track progress through hiring stages with real-time webhooks.

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Fountain with Flows360

Automate your complete HR hiring and onboarding workflow. Manage applicants, job openings, interview scheduling, and track progress through hiring stages with real-time webhooks.

Use the Fountain 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 10 actions and 4 triggers.

Available actions

  • Create Applicant
  • Delete Applicant
  • Get Applicant Details
  • Get Interview Sessions
  • Get Opening
  • Get Stage
  • List All Applicant Details
  • List All Opening Details
  • Plus 2 additional declared actions.

Available triggers

  • Applicant Webhook
  • Worker Webhook
  • Custom Attribute Webhook
  • Universal Tasks Webhook

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: Fountain
  • Package: @activepieces/piece-fountain@0.1.7
  • Exact artifact digest: sha256:b16ca9048d2e05861165535e0a3d01042c3e028b31269a6273b7fea38c351241
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Create Applicant (create_applicant), Add a new applicant to your hiring pipeline Classification: read.
  • Delete Applicant (delete_applicant), Delete an applicant by their ID Classification: read.
  • Get Applicant Details (get_applicant_details), Get complete applicant information Classification: read.
  • Get Interview Sessions (get_interview_sessions), Returns the applicant's interview sessions Classification: read.
  • Get Opening (get_opening), Get details for a specific job opening Classification: read.
  • Get Stage (get_stage), Retrieves a specific Stage Classification: read.
  • List All Applicant Details (list_applicants), List applicants with optional filters Classification: read.
  • List All Opening Details (list_openings), List job openings with optional filters Classification: read.
  • List All Stages (list_stages), Retrieves an Opening's stages Classification: read.
  • Update Applicant Info (update_applicant), Update an applicant's information Classification: read.

Trigger contracts

  • Applicant Webhook, webhook.
  • Worker Webhook, webhook.
  • Custom Attribute Webhook, webhook.
  • Universal Tasks Webhook, webhook.

Verification

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

Capability summary

Authenticationcustom
Supported objects14
Supported actions10
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential
  • Base URL Optional

Supported objects

ObjectReadWriteNotes
Create Applicant Yes No Add a new applicant to your hiring pipeline
Delete Applicant Yes No Delete an applicant by their ID
Get Applicant Details Yes No Get complete applicant information
Get Interview Sessions Yes No Returns the applicant's interview sessions
Get Opening Yes No Get details for a specific job opening
Get Stage Yes No Retrieves a specific Stage
List All Applicant Details Yes No List applicants with optional filters
List All Opening Details Yes No List job openings with optional filters
List All Stages Yes No Retrieves an Opening's stages
Update Applicant Info Yes No Update an applicant's information
Applicant Webhook Yes No webhook trigger declared by the pinned package.
Worker Webhook Yes No webhook trigger declared by the pinned package.
Custom Attribute Webhook Yes No webhook trigger declared by the pinned package.
Universal Tasks Webhook Yes No webhook trigger declared by the pinned package.

Supported actions

Create Applicant · Read

Add a new applicant to your hiring pipeline

create_applicant · Risk: low · Retry: safe

Inputs

  • name · string · Required, Applicant's full name
  • email · string · Required, Applicant's email address
  • phone_number · string · Required, Applicant's complete phone number
  • check_if_applicant_is_duplicate · boolean · Optional, Apply additional duplicate applicant blocking rules specified in company duplicate settings
Delete Applicant · Read

Delete an applicant by their ID

delete_applicant · Risk: low · Retry: safe

Inputs

  • id · string · Required, The applicant to delete (shows 50 most recent applicants)
Get Applicant Details · Read

Get complete applicant information

get_applicant_details · Risk: low · Retry: safe

Inputs

  • id · string · Required, The applicant to delete (shows 50 most recent applicants)
Get Interview Sessions · Read

Returns the applicant's interview sessions

get_interview_sessions · Risk: low · Retry: safe

Inputs

  • id · string · Required, The applicant to get interview sessions for (shows 50 most recent applicants)
Get Opening · Read

Get details for a specific job opening

get_opening · Risk: low · Retry: safe

Inputs

  • id · string · Required, The opening to retrieve details for
Get Stage · Read

Retrieves a specific Stage

get_stage · Risk: low · Retry: safe

Inputs

  • funnel_id · string · Required, The opening that contains the stage
  • id · string · Required, The stage to retrieve details for
List All Applicant Details · Read

List applicants with optional filters

list_applicants · Risk: low · Retry: safe

Inputs

  • funnel_id · string · Optional, Filter applicants by opening
  • location_id · string · Optional, Filter applicants by location
  • stage_id · string · Optional, Filter applicants by stage
  • stage · string · Optional, Filter applicants by stage name
  • labels · string · Optional, Filter applicants by labels
  • phone · string · Optional, Filter applicants by phone number
  • exclude_temporary · boolean · Optional, Whether to exclude temporary/test applicants
  • per_page · number · Optional, Number of results per page (default: 25)
  • cursor · string · Optional, Cursor for pagination
  • include_subaccounts · boolean · Optional, Whether to include applicants from sub-accounts
List All Opening Details · Read

List job openings with optional filters

list_openings · Risk: low · Retry: safe

Inputs

  • active · boolean · Optional, Filter to only active openings
  • location_id · string · Optional, Filter openings by location
  • is_hiring_funnel · boolean · Optional, Filter to only hiring funnels
  • is_sourcing_funnel · boolean · Optional, Filter to only sourcing funnels
  • is_private · boolean · Optional, Filter to only private openings
  • owner_id · string · Optional, Filter openings by owner
  • per_page · number · Optional, Number of results per page (default: 25)
  • cursor · string · Optional, Cursor for pagination
List All Stages · Read

Retrieves an Opening's stages

list_stages · Risk: low · Retry: safe

Inputs

  • funnel_id · string · Required, The opening to get stages for
Update Applicant Info · Read

Update an applicant's information

update_applicant · Risk: low · Retry: safe

Inputs

  • id · string · Required, The applicant to update (shows 50 most recent applicants)
  • name · string · Optional, Applicant's full name
  • email · string · Optional, Applicant's email address
  • phone_number · string · Optional, Applicant's complete phone number
  • data · object · Optional, Custom data fields to update (key-value pairs)
  • secure_data · object · Optional, Secure data fields to update (key-value pairs like SSN, etc.)
  • rejection_reason · string · Optional, Manually set reason for rejection

Setup

Setup

  1. Add the Fountain 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:
  • API Key (apiKey), required; stored as a sensitive connection value.
  • Base URL (baseUrl), optional.
  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-fountain@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 10 actions and 4 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 Fountain 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-fountain@0.1.7 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