--- title: "MEETOVO Integration" description: "Connect AI agents to MEETOVO, the German funnel builder for recruiting and lead generation, through its official API. Agents pull funnel submissions and route candidates and leads to the right owner." url: https://flowrunner.ai/integrations/meetovo date_modified: 2026-08-07T17:20:23-07:00 --- # MEETOVO [Forms](https://flowrunner.ai/integrations/category/documents-forms) Connect AI agents to MEETOVO, the German funnel builder for recruiting and lead generation, through its official API. Agents pull funnel submissions and route candidates and leads to the right owner. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 10 actions · API key · available [MEETOVO website](https://meetovo.de/) · [Platform Documentation](https://developers.meetovo.de/openapi/campaign-api.yaml) · Capability data verified 2026-08-04 1. A vacancy is approved and opened in the applicant tracking system 2. Agent reads the role title, location, responsibilities and hiring manager from the requisition 3. Agent matches the role with List Job Categories and reuses the saved company and job profiles by ID 4. Agent calls Generate Campaign with no ad channels selected, so only the funnel is built 5. Agent polls Get Generation Status until it completes and captures the preview URL 6. Agent posts the preview link and the generated copy into the recruiting channel 7. A recruiter approves or edits the copy before the agent regenerates with ad channels enabled ## What This Integration Enables MEETOVO is not a form builder you assemble field by field. It is a generator you commission. Generate Campaign takes company and job details, either inline or referenced from saved profiles, and produces the landing funnel and, when ad channels are selected, the matching Facebook, Instagram and Google Jobs ad assets. The unit of work is the generation request, not the page, and this [connector](https://flowrunner.ai/concepts/connectors) is shaped around that: the call is asynchronous, it returns a request ID, and a flow either polls Get Generation Status or supplies a callback URL and waits to be told. That design is what makes it worth automating. Recruiting funnels are a volume problem before they are a creative problem. A company with fourteen open roles does not need fourteen unique candidate experiences, it needs fourteen funnels that sound like the same employer and go live the week the role opened rather than the month after. Saved company and job profiles are how that consistency is enforced: send details inline once, MEETOVO creates a reusable profile automatically, and every later campaign references it by ID. Get Campaign Analytics then closes the loop with total views, applications, conversion rate, average completion time, a per-step breakdown showing where candidates drop out, and traffic sources showing which channels delivered them. Upload Image brings a logo or campaign visual in from a public URL, keeping a copy in FlowRunner file storage on the way through. There are no triggers, because the Campaign API has no webhook registration endpoints, so flows start from the applicant tracking system or from a schedule. MEETOVO sells API access as a separate subscription. ### Without FlowRunner **Funnels built by hand**: Each vacancy needs a page assembled before it can be advertised **Copy drifts per role**: The same employer sounds different across three open positions **Drop-off found late**: Where candidates abandon the funnel surfaces at the end of the campaign ### With FlowRunner **Funnels generated on approval**: The requisition triggers the build instead of a request to marketing **Shared profiles keep the voice**: Saved company and job profiles hold branding steady across campaigns **Drop-off read per step**: Per-step analytics show where candidates leave while the campaign is live ## Use Case Scenarios ### Approved vacancies that become live funnels the same week A requisition is approved in [Workable](https://flowrunner.ai/integrations/workable). The agent reads the title, location and responsibilities, resolves the closest match from List Job Categories, and calls Generate Campaign referencing the saved company profile so the branding matches everything else the employer has running. It leaves the ad channels empty on this first pass. Once Get Generation Status reports completed, the agent posts the preview URL to the recruiting channel. A recruiter reads the funnel as a candidate would, and the campaign only reaches an ad platform after they have said so. ### Weekly funnel performance that names the step to fix A scheduled flow calls List Campaigns for everything published, then Get Campaign Analytics for each over the last seven days. The per-step breakdown is the useful part: a funnel losing candidates at the availability question has a different problem from one losing them at the first screen. The agent assembles a short report per role, flags any campaign whose conversion rate has moved materially against its own prior week, and posts it to the hiring channel with the dashboard link. Nobody opens six dashboards to find the one that needs attention. ### Profile hygiene before the campaigns pile up Before generating anything, the agent calls List Company Profiles and List Job Profiles and checks whether a profile already covers this employer and this role. Reusing a job profile keeps the role description identical across repeat campaigns for the same vacancy, which matters for an employer hiring the same position in four cities. Where a profile is missing a logo, the agent calls Upload Image with the asset from the brand store and reports what it filled in. This is unglamorous work and it is exactly the work that decides whether the tenth campaign looks like the first. ## Human-in-Loop Highlight Selecting ad channels on Generate Campaign changes what the call does in a way that deserves a person's attention. Without them, MEETOVO builds a funnel that sits at a preview URL and reaches nobody. With them, it also produces Facebook, Instagram and Google Jobs ad assets: AI-written copy describing a real job at a named employer, going out under that employer's brand to an audience of people who may currently work for a competitor, or for them. Recruitment advertising is one of the few marketing surfaces where a wrong sentence about pay, hours or seniority is a legal and reputational matter rather than a conversion one. There is also a status this API returns that says exactly why this matters: partially created, meaning some assets succeeded and others did not, which is a state no automated flow should resolve by guessing. MEETOVO ships the gate as a documented option, so FlowRunner uses it rather than inventing an approval layer on top. The agent generates with ad channels empty, which the vendor documents as the way to build the funnel without generating any ads. It polls Get Generation Status, captures the live and preview URLs, and treats the review as a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step, messaging the recruiter: "Warehouse Team Lead, Duisburg, funnel generated from job profile 219 and ready at the preview link. Ad copy is drafted for Facebook, Instagram and Google Jobs. Approve to publish the ads, edit the copy first, or run the funnel on its own for now?" A recruiter reads the copy as a candidate would, answers, and only then does the agent regenerate with channels selected. The building is automated. What goes out under the employer's name is not. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 10 actions ### Campaigns 3 - **Generate Campaign** Starts MEETOVO's AI generation of a recruiting campaign, building the landing funnel and, when channels are selected, the matching Facebook, Instagram and Google Jobs ad assets. Company and job details can be supplied inline or referenced from saved profiles by ID. Generation is asynchronous, returning a request ID to poll with Get Generation Status, or notifying an optional callback URL instead. Leaving the ad channels empty builds the funnel without generating any ads, which is the safe first pass before a human approves the copy. - **Get Generation Status** Polls the progress of a generation request. While work is under way the status is pending or processing, and on completion the response carries the new campaign's ID with its live, preview and dashboard URLs. A partially created status means some assets succeeded and others did not, which is a case to surface to a person rather than retry blindly. - **List Campaigns** Retrieves the campaigns in the account with offset and limit pagination, narrowable by publication status, by the company or job profile they were built from, and by a creation date range. Each campaign reports its live, preview and dashboard URLs. Used as the enumeration step for reporting flows. ### Analytics 1 - **Get Campaign Analytics** Retrieves funnel performance for one campaign over a required date range, covering total views, applications, conversion rate and average completion time. The per-step breakdown shows where candidates drop out and the traffic sources show which channels delivered them, which together point at what to fix first rather than only reporting that something is wrong. ### Companies 2 - **List Company Profiles** Retrieves the saved company profiles on the account. Profiles are created automatically the first time a campaign is generated with inline company details, and reusing one by ID keeps branding consistent across campaigns. - **Get Company Profile** Retrieves one saved company profile by identifier, returning the branding and description MEETOVO reuses when generating. Used to confirm a profile is complete before pointing a new campaign at it. ### Jobs 3 - **List Job Profiles** Retrieves the saved job profiles on the account. Like company profiles these are created automatically from inline job details, and reusing one keeps the role description identical across repeat campaigns for the same vacancy. - **Get Job Profile** Retrieves one saved job profile by identifier, including its title, category and responsibilities. Used to review the role definition MEETOVO will generate copy from before it generates it. - **List Job Categories** Retrieves the job categories and sub-categories MEETOVO recognises. Supplying a matching category and sub-category when generating improves how well the generated copy and the ad audience target the role. ### Uploads 1 - **Upload Image** Uploads an image to MEETOVO from a publicly reachable URL and returns the hosted URL to use as a company logo or campaign visual. The file is fetched, stored in FlowRunner file storage for traceability, then forwarded to MEETOVO as a multipart upload. ## Frequently Asked Questions ### What can FlowRunner do with MEETOVO? FlowRunner agents can run Generate Campaign, Get Generation Status, and List Campaigns in MEETOVO, plus 7 more actions. ### Does connecting MEETOVO to FlowRunner require OAuth? No. MEETOVO connects to FlowRunner with an API key, no OAuth flow required. ### Can MEETOVO trigger a FlowRunner workflow automatically? MEETOVO doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at MEETOVO?** This integration exposes MEETOVO to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/meetovo. Site index: https://flowrunner.ai/llms.txt