What TaaSFlow connects to today

Lets an 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.

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.

Keeps billing state truthful: successful payments, refunds and disputes update your account without anyone re-keying them.

Connection method

Signature-verified webhooks from the payment provider, processed once per event so retries cannot double-apply.

Data exchanged

Inbound only: payment, refund and dispute events, plus the amount and the account they belong to.

Permissions required

None on your side — this runs between TaaSFlow and the payment provider.

Health visibility

Payment events and their applied state are visible to TaaSFlow administrators in the payments ledger.

Push hiring events — shortlist released, interview scheduled, 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.

Mirrors inbound hiring enquiries into a CRM so commercial follow-up never depends on someone remembering.

Connection method

Authorised once by TaaSFlow through a managed connector; tokens are refreshed for us and never handled in the app.

Data exchanged

Outbound: company name, contact name and email, the role discussed and where the enquiry came from.

Permissions required

Create and update records in the connected CRM workspace.

Health visibility

Probed from the admin integration health page: reachability, authorisation and the provider's own error text.

Books intro calls and interview slots against real availability instead of an email thread.

Connection method

Managed connector authorised by TaaSFlow, plus an embedded scheduling flow on our public pages.

Data exchanged

Outbound: invitee name, email and the meeting type. Inbound: the confirmed slot and its time zone.

Permissions required

Read scheduling links and availability, and read booked events.

Health visibility

Probed from the admin integration health page before a booking page is shown.

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.

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. Failed posts are logged server-side and swallowed so nothing user-facing breaks.

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

Connection method

Hosted checkout. Card details are entered on the provider's own page and never reach TaaSFlow.

Data exchanged

Outbound: the plan or pilot being bought, the amount and your billing email. Inbound: payment outcome and receipt reference.

Permissions required

None beyond completing your own checkout.

Health visibility

Probed from the admin integration health page, including whether plan prices are present before anyone is sent to checkout.

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.

Measures how the public site performs so we can fix what confuses visitors. Applies to taasflow.com, not to your hiring data.

Connection method

Browser tags loaded only after the regional consent gate allows the relevant category. Declining consent means the tags never load.

Data exchanged

Outbound: page views, referrer and anonymous interaction events. Consent state is sent with every measurement call.

Permissions required

Your own consent choice, changeable at any time.

Health visibility

Tag load state is visible to TaaSFlow administrators in the tracking policy panel.

Answers dropout, speed and spend questions from your own pipeline data — no external analytics product involved.

Connection method

Built in. Nothing to connect.

Data exchanged

None leaves the platform. Figures are computed from your own roles, candidates and decisions.

Permissions required

Your workspace role decides what you can see.

Health visibility

Every metric states its own freshness and says so plainly when there is not enough data to answer.

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.

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.

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.