Integrations
What actually connects, and what does not.
Most integration pages are a wall of logos that quietly means we have heard of these companies. This one is a list you can check. What connects today is named with the limit that matters. What does not connect is named too, in the same size type, because you would find it in week one anyway and we would rather lose the evaluation now than the account later.
Connected today
Everything below moves real data, right now.
Each one is printed with its limit attached, because the limit is the part a logo wall leaves out. If it is not on this list, it is in the section under it.
Data in · scheduled · nothing for you to set up
Public job feeds, read one way
This is not a connection to your systems. Nothing is written back to you, nothing is authorised by you, and there is nothing to configure in your account.
Futureful builds its index by reading job postings that are already public. That includes employer career sites published through Greenhouse, Lever, Ashby, SmartRecruiters, Workday, Pinpoint and Phenom, the federal USAJOBS feed, and licensed job-search APIs. Ingestion runs on its own schedule so the market picture is already there when you open the console. It is the reason we can tell you what is being posted around you, and it is the only reason.
Data out · your pipeline and your shortlist
CSV export, with the disclosure decided server-side
Available on your pipeline and your shortlist. There is no export of postings, no PDF, and no report pack.
The file honours the filters you have on screen, because the export reuses the same query vocabulary the list itself uses rather than a mapping table that can drift from it. The column set is derived on the server from your session and there is no parameter to request columns, so a download cannot widen its own disclosure. Rows still waiting on guardian consent are floored out. If the export cannot run it returns a refusal, never a file with a valid header and no rows, because an empty CSV is indistinguishable from an honest nothing matched.
Delivery out · scheduled
Email that carries counts, never people
Email is the only outbound channel. There is no SMS to employers, no chat message, and no push to a third-party tool.
A Monday digest of your own numbers, and a nudge when someone in your pipeline has been waiting on you longer than they should. Both carry aggregate counts only: no candidate name and no personal detail ever rides in the body. Both honour the notification preferences on your account, and a quiet week sends nothing rather than manufacturing a reason to appear in your inbox.
Not connected
The absences, said plainly.
If you are comparing Futureful against a tool that syncs with your ATS, this is the section that decides it. Every line below is a real absence in the shipped product, not a limitation of a plan you could upgrade out of.
Your ATS or your HRIS
This is the important one, and it is worth being exact. We read job postings that companies publish publicly through platforms like Greenhouse and Workday. We do not connect to YOUR instance of any of them. Nothing you do in Futureful appears in your ATS, nothing in your ATS appears here, and there is no hire write-back. If an ATS sync is what you are shopping for, we are not that product today.
Slack, Teams, and webhooks
None of these exist in the product. There is no outbound webhook, no chat notification of any kind, and no Zapier or middleware listing.
A public or partner API
There is no employer API. CSV export on your pipeline and your shortlist is the only way data leaves your account in bulk.
Calendar sync, for employers
Futureful does have a real two-way Google Calendar and Microsoft 365 connection, built and working, and it is on the job-seeker side of the platform only. An employer account cannot reach it, so we do not count it here. Interviews you arrange live in your pipeline, not in your calendar.
SSO and SAML
Not built. If your security review requires SAML, it is a real blocker today and we would rather you hear it from this page than from an implementation call.
Billing and seat provisioning
There is no payment, subscription or seat-provisioning system in the product. Founding partners are set up before any of that exists, which is part of what the programme is.
Not built · nothing in this section exists yet
The founding-partner roadmap.
None of the items below is in the product. They are here so you can see what is being considered and, more to the point, so you can change the order. We are not attaching dates to them, because a date on a pre-launch roadmap is a guess wearing a suit. Founding partners get direct influence over what gets built next, and this is the list that influence applies to.
ATS write-back
Pushing a hire or a stage change back into your system of record, starting with the platforms whose public feeds we already read.
SSO and SAML
Plus the security-review artifacts that tend to arrive with it. Named most often by the largest employers we have spoken to.
Webhooks and chat delivery
So a pipeline event can reach the channel your team already works in, instead of only an inbox.
A data API
Programmatic access to the market figures you can read on screen today, for teams who want them in their own reporting.
Calendar for employers
Extending the seeker-side connection to employer accounts, so an interview lands in the right calendar.
Shape what connects next
Tell us which integration is the one that decides it.
If a missing connection on this page is a blocker for you, that is genuinely the most useful thing you can tell us before launch. It is a far better use of a first conversation than us walking you through what already works, and it is how the roadmap above gets ordered.
Live demo · real data · honest-empty where the index is thin