Interhyp Gruppe
FinanceConnect AI agents to the Interhyp Submission API from German mortgage broker Interhyp AG. Agents submit financing applications, send submission commands, read pre-scoring results, and download the documents a submission produced.
What This Integration Enables
Filing a financing application in Germany is a regulated act performed on a named borrower's behalf, and the Interhyp Submission API is shaped accordingly. Twenty-seven of the thirty-one operations here read. Three write, and each of them writes by sending a command object that Interhyp processes asynchronously and returns a command ID for, which you resolve with Get Command. That asymmetry is not a gap in the connector. It is the vendor's own statement about which side of this interface a machine belongs on, and FlowRunner builds the same way: the agent does the assembly, the reading and the chasing, and a person owns the moment the case leaves the building.
On the read side an agent can pull a financing application whole, with applicants, applicant relationships, households, estates, financial standings, consultation, venture, offer and informers embedded in a single call. From there it follows the submission through status, overview and logbook, the point-in-time snapshot of exactly what was submitted, and the household budget, financing condition and property lending value calculations behind it. Handover reports and submission documents come back as PDFs stored in FlowRunner file storage and returned as URLs, and Get Submissions Protocol gives the partner-wide audit log. Two clarifications worth stating plainly, because the operation names invite the wrong reading: Get Pre-Submission Checks retrieves a pre-scoring result, it does not run a new check, and the document operations are download only. There is no upload action in this surface, so supporting documents are read and filed elsewhere, not attached through the connector. The service publishes no webhook subscription and this connector ships no trigger, so an agent watching a case for movement polls Get Submission Status or Get Submission Logbook on a schedule rather than waiting for an event.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Pre-scoring before the case is packaged
An advisor marks a case ready in the partner's own CRM. The agent calls Get Pre-Submission Checks for that intent and the intended loan partner, filters by check status, and reads the failing and warning items. It then pulls the application with Get Financing Application and maps each finding to the specific applicant, estate or financial standing it concerns, and posts the mapped list to the advisor. The advisor sees which loan partner will balk at what while the case is still editable, rather than after a submission has been created and revoked.
Status and document collection across an active book
A partner has dozens of submissions in flight. On a schedule the agent runs List Submissions with a time filter, calls Get Submission Status on each, and writes the current state into the partner's pipeline board. Where a submission has moved, it reads Get Submission Logbook for what changed and Get Handover Reports for new documents, downloads them with Download Handover Report and Download Document Binary into FlowRunner file storage, and links the stored PDFs onto the case record in Airtable or Notion. Nobody opens the portal to find out what happened overnight.
A filing that waits for a person
The upstream system says a case is complete. The agent builds the submission command, runs Get Pre-Submission Checks one more time so the findings attached to the request are current, retrieves the exact application state it would be filing with Get Financing Application, and then stops. It does not send. The advisor receives the case, the checks and the target loan partner in one message and decides. On approval the agent runs Send Submission Command, resolves the asynchronous result with Get Command, and records the outcome. The human-in-the-loop step is not a courtesy notification after the fact. It sits between the assembled case and the filing.
Human-in-Loop Highlight
Send Submission Command is the gate, because a submission is a filing made on a named borrower's behalf to a named loan partner, and undoing one is itself an act. The only route back is another Send Submission Command carrying a revoke, which leaves a revoked submission and a logbook entry that both the partner and the loan partner can read. There is no quiet retry. So the agent assembles everything and hands over the decision. It attaches the embedded application from Get Financing Application, the pre-scoring findings from Get Pre-Submission Checks filtered to anything not passing, and the loan partner ID, then asks the advisor in Slack or by email: "Case [reference] for [applicant names] is ready to file to [loan partner]. Two checks are still open, listed below. File it, hold for the missing income document, or send it to a different partner?" The advisor answers. On approval the agent sends the command, polls Get Command for the processing result, and writes the submission ID and the approver's name back to the case. Reading, chasing and packaging run unattended. The filing does not.
Agent Capabilities
31 actionsService
1- Get Service Info Returns the Submission API service status and the version of the API specification currently in use. Useful as a connectivity and authentication check before a flow commits to a longer sequence.
Financing Applications
14- Get Financing Application Retrieves a single financing application by its ID. Set Embed to include all sub-resources (applicants, estates, financial standings) inline; otherwise only basic fields and links are returned.
- Get Applicants Retrieves the list of applicants (borrowers) belonging to a financing application.
- Get Applicant Retrieves a single applicant of a financing application by applicant ID.
- Get Applicant Relationships Retrieves the relationships between the applicants of a financing application (for example marital or household relationships).
- Get Households Retrieves the household information of the applicants of a financing application.
- Get Estates Retrieves the estates (properties) associated with a financing application.
- Get Estate Retrieves a single estate (property) of a financing application by estate ID.
- Get Financial Standings Retrieves the combined financial standings (income, assets, existing loans) of the applicants of a financing application.
- Get Consultation Retrieves the financing consultation details linked to a financing application.
- Get Venture Retrieves the financing venture (the purpose and structure of the financing) for a financing application.
- Get Offer Retrieves the financing offer associated with a financing application.
- Get Informers Retrieves the consultation informers (the advisors or contacts involved) for a financing application.
- Create Financing Application Creates a new financing application by sending a command object. The command shape is defined by the Interhyp Submission API; pass the full command payload including its type discriminator and data.
- Send Financing Application Command Sends a command to an existing financing application, for example to create or replace its submission. The command shape is defined by the Interhyp Submission API command schema.
Submissions
10- List Submissions Lists active (non-revoked) submissions for the authenticated financing partner, optionally filtered by a time range. Uses cursor-based pagination and returns up to 20 items by default, 50 at most. Page with the After or Before cursor from the response.
- Get Submission Retrieves a single submission by its ID. Set Embed to include all sub-resources inline; otherwise only basic fields and links are returned.
- Get Submission Status Retrieves the current status of a specific submission. This is the operation a polling flow calls to detect movement, since the service ships no trigger.
- Get Submission Overview Retrieves the overview of a submission, summarizing its key financing and applicant details.
- Get Submission Logbook Retrieves the logbook entries (activity history) of a submission, which is what a flow reads to find out what changed rather than only that something did.
- Get Submitted Financing Application Retrieves the financing application exactly as it was submitted within a specific submission, as a point-in-time snapshot.
- Get Submission Calculation Retrieves calculation data for a submission by calculation type: household budget, financing condition, or property lending value.
- Get Handover Reports Retrieves the list of handover reports available for a submission. Each entry includes the report name used to download the report as PDF.
- Download Handover Report Downloads a specific handover report of a submission as a PDF and stores it in FlowRunner file storage, returning a URL to the stored file. Use the report name from Get Handover Reports.
- Send Submission Command Sends a command to an existing submission, for example to revoke it. The command shape is defined by the Interhyp Submission API command schema. This is the action routed for human sign-off.
Pre-Submission Checks
1- Get Pre-Submission Checks Retrieves the collection of pre-submission checks (pre-scoring) for a given intent ID and loan partner ID, giving an early indication of whether a submission can be created. Filter by check status to isolate what is still failing.
Commands
1- Get Command Retrieves an existing command by its ID, including its processing status. Use this to resolve the result of an asynchronously processed command returned by a create or modify action.
Documents
4- Get Documents Metadata Retrieves the metadata for all documents relevant to a submission, including each document ID used to download the binary content.
- Download Document Binary Downloads a specific submission document from the documents metadata list as a PDF and stores it in FlowRunner file storage, returning a URL to the stored file.
- Download Uploaded Document Downloads a specific uploaded submission document as a PDF and stores it in FlowRunner file storage, returning a URL to the stored file.
- Get Submissions Protocol Retrieves the submissions protocol, the audit log of submission activity for the authenticated financing partner.
Frequently Asked Questions
What can FlowRunner do with Interhyp Gruppe?
FlowRunner agents can run Get Service Info, Get Financing Application, and Get Applicants in Interhyp Gruppe, plus 28 more actions.
Does connecting Interhyp Gruppe to FlowRunner require OAuth?
Interhyp Gruppe uses a custom authentication method to connect to FlowRunner.
Can Interhyp Gruppe trigger a FlowRunner workflow automatically?
Interhyp Gruppe doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Interhyp Gruppe
$100 in credits. No card required. Connect in minutes.