Skip to main content

Integrations

What TaaSFlow connects to today

Each listing states its purpose, how the connection is made, what data crosses the boundary and what permissions it needs. Anything not built yet is marked Planned. Systems TaaSFlow runs for itself, such as our own billing and website analytics, are not listed here. The TaaSFlow workspace includes its own applicant tracking. Direct sync with an external ATS is planned, not built. Roles are published on the TaaSFlow job board. Outbound distribution to external job boards is planned, not built.

Last reviewed 7 October 2026Trust Center

Connections you can use

Agent connectivity (MCP)

Agent connectivity (MCP)

Agent connectivity (MCP)

Available

Lets an external AI assistant such as Claude or ChatGPT read your roles, shortlists and candidate evidence with your own permissions.

Connection method
Model Context Protocol over HTTPS. You add the TaaSFlow server in your assistant, sign in with your TaaSFlow account and approve the connection on a consent screen.
Data exchanged
Read-only: your hiring roles and their requirements, candidates released to you, and screening summaries with supporting evidence. Nothing is written back.
Permissions required
Your own TaaSFlow sign-in. The connection sees exactly what you see in the workspace — candidates not yet shared with you stay invisible.
Health visibility
No health panel yet. A failed connection surfaces as an error in your assistant.

API

Intake and application endpoints

API

Custom setup

Submit a hiring brief or check an application's progress from your own site or internal tooling instead of our forms.

Connection method
HTTPS JSON requests to documented public endpoints, validated against a strict schema. We agree the payload with you during onboarding.
Data exchanged
Inbound: role brief, contact details, hiring context. Outbound: submission reference and current processing state.
Permissions required
Agreed in writing during onboarding. Application status lookups return only the reference holder's own state.
Health visibility
Failures return an explicit error on the response.

Email

Transactional email

Email

Available

Sends the messages a hiring process depends on: welcome mails, application confirmations, approval requests, receipts and the weekly digest.

Connection method
Sent from a delegated TaaSFlow sending subdomain with domain authentication in place. Nothing to configure on your side.
Data exchanged
Outbound: recipient name and address, and the content of the notification itself.
Permissions required
None on your side. Recipients control their own notification preferences in the workspace.
Health visibility
Sender-domain verification and send failures are probed and logged; delivery problems appear in the admin email log.

Messaging

Microsoft Teams

Messaging

Beta

Posts new applications and inbound enquiries into a Teams channel so the team sees movement without opening the workspace.

Connection method
Managed connector authorised once for a specific team and channel. Notifications are best-effort and never block an application.
Data exchanged
Outbound only: a short notice with the role, the candidate reference and a link back into TaaSFlow.
Permissions required
Post messages to the one channel you nominate.
Health visibility
No health probe yet. If a post fails, the application or enquiry still goes through.

Authentication

Google sign-in

Authentication

Available

Sign in to the workspace with an existing Google account instead of another password.

Connection method
OAuth sign-in on the TaaSFlow login page.
Data exchanged
Inbound: your name, email address and profile picture. No mail, calendar or file access is requested.
Permissions required
Basic profile and email address only.
Health visibility
Sign-in failures are reported on the login screen as they happen.

Planned, not built yet

Webhooks

Outbound webhooks to your systems

Webhooks

Planned

Push hiring events — shortlist released, offer accepted — into your own systems as they happen.

Not available yet. The internal event model exists; subscriber management, retries and signing are not built. No delivery date is promised.

No setup documentation — nothing to set up yet.

Payments

Payments

Payments

Planned

Takes payment for a pilot or a plan before a role goes live, with tax calculated at checkout.

Not available yet. Online checkout is switched off for now. Packages are requested and invoiced by TaaSFlow directly. No date is promised for turning it on.

Applicant tracking systems

Applicant tracking system sync

Applicant tracking systems

Planned

Two-way sync of roles, candidates and stage changes with an existing ATS so TaaSFlow is not a second system of record.

Not available yet. No ATS connector is implemented. If you need one, tell us which system you run — we prioritise by demand, not by logo.

No setup documentation — nothing to set up yet.

Job distribution

Job board distribution

Job distribution

Planned

Publish a live role to external job boards and aggregators from the same place you approve it.

Not available yet. Roles are published on the TaaSFlow job board today. No outbound board or aggregator feed is implemented.

No setup documentation — nothing to set up yet.

Data sources

Third-party candidate data sources

Data sources

Planned

Enrich candidate records from external data providers to widen discovery beyond direct applications.

Not available yet. Scoring today uses evidence taken from material the candidate submitted. No external enrichment source is connected.

No setup documentation — nothing to set up yet.

Need a connection that is not listed?

Tell us which system you run and what should flow between it and TaaSFlow. We build integrations by demand, and we will tell you honestly whether it is on the roadmap.

Run your role.

  • One role, run end to end.
  • Up to 10 candidates, reviewed by a recruiter.
  • Usually 5 business days from an approved brief.

Or start a $699 pilotSend us a message