Our partners
Integration partners
Your system manages applicants, calendars or identities; flynne runs the assessments in between. Together we close the gap where spreadsheets and email chains live today.
A two-way integration
flynne reports status back in real time: your customers keep their system of record and gain the whole assessment operation alongside it.
Shared enterprise customers
flynne addresses large groups and mid-sized companies in the German-speaking market: your integration becomes part of every tender response and every offer.
Technically straightforward
REST APIs, webhooks and proven connector patterns (SAP SuccessFactors, SmartRecruiters and BeeSite are live). We build with you, not only against you.
How the integration runs
Four steps, usually over a few weeks, depending on how much time your engineering team has.
A technical conversation
Which objects should flow, in which direction, how often? With an applicant tracking system it is usually applicants and status; with a test provider, references to results. Developers have that conversation with developers, not sales with sales.
A test environment
You receive access to an environment with sample data and the interface documentation. Breaking things there is allowed and expressly welcome.
Build it and test it
We build with you, not against you: in the existing integrations we took on half the debugging each time, because both sides make assumptions about the other that turn out to be wrong.
Listing
Once the connection is stable, your system appears in the integrations overview and in offers. Not before: a connection that exists only on paper costs both sides trust.
What you bring
A documented interface
REST with webhooks is the simplest case. Other routes work too but need more coordination. What does not work are file exports that somebody triggers by hand.
A technical contact we can reach
Not for questions answered once a week. Debugging an integration consists of short rounds, and if a reply takes five days, the project takes months instead of weeks.
A test system
With data you can work on. An integration first tested in production is not a project but a risk.
A willingness to maintain versions
APIs change, on both sides. We announce changes in advance and expect the same. What we do not want is an integration that quietly fails one morning.
Common questions
Which data flows between the systems?
As little as possible: applicant data needed for scheduling, and the status back. Raw data from procedures, such as judgements, test scores and observations, deliberately stays in flynne and does not flow into the applicant tracking system. That is a decision of principle: an ATS is no place for raw assessment data.
Who operates the connection?
The connector runs at our end, in our data centre in Germany. You provide the interface; we provide the integration and run it, monitoring and error reporting included.
What happens when we change our API?
Then we need notice. We keep versions running in parallel as long as customers work on the old one. What matters is telling us beforehand; a silent change surfaces during an assessment day, which is the worst possible moment.
Does the data stay in the EU?
Yes, exclusively. Operated in Germany, a German contracting party, a data processing agreement under Article 28 GDPR. For your customers that is often the first thing procurement asks.
Does the integration cost anything?
We carry the development work on the standard connector; customer-specific adjustments are costed in the project. Everything beyond that, such as joint marketing, support routes or being named in offers, we discuss case by case.
Let us talk about the interface.
Write briefly which system you want to connect and which interface it brings. We reply within one working day, with a developer in the conversation rather than a form letter.
We reply within one working day.