Surense
Identity & SecurityConnect AI agents to Surense, the Israeli pension and insurance licensee compliance registry. Agents create and update licensee records, retrieve their license documents, and validate that an agent is authorized before a flow proceeds.
What This Integration Enables
Surense is not a CRM that happens to hold agents. It is a registry of who is permitted to sell regulated pension and insurance products, and that difference decides how a flow built on it should behave. A wrong contact record costs a misaddressed email. A wrong licensee record means an agency believes someone is authorized when the regulator's registry says otherwise, and the agency finds out during a review rather than beforehand. Every design choice on this page follows from that.
The connector covers two surfaces. The administrative surface operates on any licensee in the caller's agency. List Licensees returns a flat roster and Search Licensees adds filtering, sorting, and pagination with a page window capped at 50. Get Licensee returns the full record, Create Licensee and Update Licensee handle writes, and Get Licensee Documents, Upload Licensee Document, and Get Licensee Document URL cover the yearly license documents held on file. The self service surface does the same work for the licensee linked to the authenticated user, through Get My Licensee, Update My Licensee, Get My License Documents, Upload My License Document, and Get My License Document URL. Get My Licensee returns null rather than raising when no licensee is linked, so a flow can branch on it cleanly. Entity type comes back as one of the Israeli entity codes עמ for an individual, חפ for a private company, or חצ for a public company. List License Types returns the raw category codes the update operations accept, so a flow can validate a license category against the platform's own vocabulary instead of a hardcoded list.
The action worth building around is Check Licensee Validity. It validates a license or company number against the regulator's public registry and returns that registry's own view of the person: name, contact information, license type, and the pensioni, clali, and yami coverage flags. It creates nothing. That makes it safe to call as often as you like, and it is the only action here that reaches outside the agency's own data for an answer. There are no triggers on this connector. Detecting change means calling Search Licensees on a schedule sorted on a date field and comparing against the previous run, which is the pattern the extension's own documentation recommends. Authentication is OAuth 2.0 client credentials configured as service settings, with no user consent screen, and all endpoints are agency scoped so a caller sees only its own agency's licensees unless the credentials hold an administrative role.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Verify before you add, not after
An agency signs a new agent and the record starts life in a spreadsheet or an operations board. The agent reads the pending rows from Airtable and calls Check Licensee Validity for each license or company number. That single call answers a question the agency cannot answer from its own data: does this number exist in the regulator's registry, whose name is attached to it, and which product categories does its coverage actually span. Numbers that come back clean and consistent proceed to Create Licensee with the agency, ID number, and license or company number that the create operation requires. Numbers that come back with a different name, a narrower coverage set, or nothing at all never reach a write. They go to the compliance owner as a short list with both versions side by side.
Annual license documents collected without a chase
Every licensee needs a yearly license document on file, and the collection of those PDFs is usually a mail merge followed by a month of reminders. A scheduled flow calls Search Licensees for the active roster, then Get Licensee Documents per licensee to see which license years already have a document, producing an exact gap list instead of a blanket reminder to everyone. Agents who are missing a year get one message naming that year. When a document arrives, the agent calls Upload Licensee Document against the correct license year, which fetches the file from a supplied URL and stores it against the record. At audit time the pack is assembled with Get Licensee Document URL, which returns short lived presigned download links, so the flow fetches each file promptly rather than passing links around that will expire in someone's inbox.
A self service surface an agent can actually use
Rather than routing every detail change through a compliance mailbox, an agency exposes a small portal to its own licensees. When a licensee signs in, the flow calls Get My Licensee, which returns their full record or null when no licensee is linked to the account, so the portal renders the right thing either way. The licensee corrects a phone number or a mailing address and the agent calls Update My Licensee, which changes only the fields supplied and leaves the rest untouched. They upload this year's license document and the agent calls Upload My License Document against the right license year. What the self service surface deliberately does not do is change license type or coverage. Those fields describe what the regulator permits, and a licensee editing their own permissions is not a workflow, it is a control failure.
Human-in-Loop Highlight
Create Licensee is where this connector stops being a data integration and starts being a compliance decision. The write itself is validated: the license and company numbers are checked against the regulator's public registry as part of the create. What the platform cannot check is whether the coverage the registry reports matches the work the agency is about to hand this person. Check Licensee Validity returns the pensioni, clali, and yami flags exactly as the registry holds them, and the interesting case is not the outright rejection, it is the partial match. The number is genuine, the name is right, and the coverage set is narrower than the products the agency intends this agent to sell. Nothing in the API treats that as an error, because from the registry's point of view nothing is wrong. The record would be created, the agent would appear on the roster, and the mismatch would sit there silently until someone assembled a review. So the agent stops short of the write. It posts both records to the compliance owner: "Registry match for license 3041782. Name matches. Registry shows pensioni and clali coverage; the onboarding request has this agent selling yami products as well. Create the licensee with the registry's coverage, hold pending clarification, or escalate?" The compliance owner answers, and the agent calls Create Licensee only for the outcome that was chosen, and only with the coverage that was approved. The same pause applies to Update Licensee, which is an administrative operation that rewrites the record the agency's compliance file rests on. This is what human-in-the-loop is for. The agent did the registry lookups, the diffing, and the assembly across the whole roster. It handed back the one judgment that carries consequences the agency would have to answer for.
Agent Capabilities
15 actionsLicensee Registry
5- List Licensees Returns every licensee belonging to the caller's agency as a flat list, each with id, name, entity type, license number, and active flag. Entity type comes back as one of the Israeli entity codes עמ for an individual, חפ for a private company, or חצ for a public company. Use Search Licensees when filtering, sorting, or pagination is needed.
- Search Licensees Searches licensees in the caller's agency with an array of filters, each a field, a value, and a comparison operator, combined with And or Or, plus an optional sort field and direction and a page window. The page size, End Row minus Start Row, must be 50 or less. Returns the matching licensees with a hasNextPage flag and the total count. Sorted on a date field, this is also the change detection pattern for a connector with no triggers.
- Get Licensee Retrieves a single licensee by UUID, returning identity and license numbers, entity type, contact details, license type, the pensioni, clali, and yami coverage flags, and audit metadata. Only licensees within the caller's agency are visible unless the caller holds an administrative role.
- Create Licensee Creates a licensee, individual or company, within the specified agency. The license or company number, the ID number, and the agency are required; other contact and operation fields are optional. The license and company numbers are validated against the Israeli regulator's public registry as part of the create.
- Update Licensee Updates an existing licensee by UUID, an administrative operation that changes only the fields supplied and leaves omitted fields untouched. License Type accepts one of the Israeli license categories returned by List License Types.
License Documents
3- Get Licensee Documents Retrieves the list of yearly license documents on file for a licensee by UUID, an administrative operation. Each entry describes one year's document with its license year, document name, MIME type, and upload metadata. The action that turns "who is missing a document" into an answerable question.
- Upload Licensee Document Uploads a yearly license PDF for a licensee by UUID, an administrative operation. The file is fetched from a supplied URL and stored against the given license year, and the created license document record is returned.
- Get Licensee Document URL Generates a short lived presigned download URL for a licensee's document for a given year, an administrative operation. The URL grants temporary read access and expires, so a flow should fetch the file rather than pass the link onward.
Self Service
5- Get My Licensee Retrieves the licensee linked to the currently authenticated user. A user is not required to be linked to a licensee, and when none is linked the operation returns null rather than raising an error, which makes it safe as the first call in a portal flow.
- Update My Licensee Updates the licensee linked to the currently authenticated user, changing only the fields supplied. License Type accepts one of the Israeli license categories.
- Get My License Documents Retrieves the list of yearly license documents belonging to the currently authenticated licensee, each with its license year, document name, MIME type, and upload metadata.
- Upload My License Document Uploads a yearly license PDF for the currently authenticated licensee. The file is fetched from a supplied URL and stored against the given license year.
- Get My License Document URL Generates a short lived presigned download URL for the currently authenticated licensee's document for a given year. The URL expires, so use it promptly.
Regulator Validation
2- Check Licensee Validity Validates a licensee against the Israeli regulator's public registry by license or company number without creating any record, returning the registry's own details for that number: name, contact information, license type, and the pensioni, clali, and yami coverage flags. It writes nothing, which makes it cheap to call before every decision that depends on it.
- List License Types Returns the available Israeli insurance and pension license types as their raw category codes, which are the values the update operations accept. Read it rather than hardcoding a list that will drift.
Frequently Asked Questions
What can FlowRunner do with Surense?
FlowRunner agents can run List Licensees, Search Licensees, and Get Licensee in Surense, plus 12 more actions.
Does connecting Surense to FlowRunner require OAuth?
Surense uses a custom authentication method to connect to FlowRunner.
Can Surense trigger a FlowRunner workflow automatically?
Surense doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Surense
$100 in credits. No card required. Connect in minutes.