--- title: "Meetime Integration" description: "Connect AI agents to Meetime, a Brazilian sales engagement platform for prospecting cadences. Agents edit leads and add them to a cadence, and read the calls, demos, and prospecting activity that moved a deal forward." url: https://flowrunner.ai/integrations/meetime date_modified: 2026-08-11T09:36:14-07:00 --- # Meetime [Sales Outreach](https://flowrunner.ai/integrations/category/crm-sales) Connect AI agents to Meetime, a Brazilian sales engagement platform for prospecting cadences. Agents edit leads and add them to a cadence, and read the calls, demos, and prospecting activity that moved a deal forward. 20 actions · API key · available [Meetime website](https://meetime.com.br/) · [Platform Documentation](https://meetime.readme.io/) · Capability data verified 2026-08-11 1. A scheduled poll reads new qualified contacts from the source of record 2. List Custom Fields returns the field keys and the PICKLIST option identifiers the enrollment needs 3. List Leads filtered by email confirms the person is not already in a running prospection 4. List Cadences returns the target cadence, its owner, and the cadence token the enrollment will use 5. SDR manager receives the resolved batch, the cadence name, and the first touch the cadence will send 6. Manager confirms the cadence and the list, and only then does Add Lead to Cadence start the prospections ## What This Integration Enables Meetime is built around the cadence, the fluxo: a designed multi-touch sequence that an SDR runs against a lead, step by step, with the prospection as the record of that journey. Understanding that shapes what this [connector](https://flowrunner.ai/concepts/connectors) is good for. It is not a call logger and it is not a dialer. The write surface is deliberately narrow. Agents enroll a lead in a cadence, correct a lead record, and manage webhook subscriptions. Everything else reads: leads, cadences, activity templates, loss reasons, prospections, prospection activities, opportunity feedback, calls with their AI-generated summaries and recording URLs, demos, users, custom fields and account information. Calls and demos in particular are read only here. There is no operation that creates a call or logs a demo, so a workflow reports on prospecting activity, it does not manufacture it. Two behaviours matter more than the operation list. Edit Lead is a full replacement: any editable field omitted from the request has its current value erased, which turns a well-meaning single-field correction into data loss unless the agent reads the lead first and sends everything back. And Add Lead to Cadence authenticates differently from every other operation, using the cadence's own token rather than the account API token, with startImmediately defaulting to true when omitted. On triggers, be clear about what this integration does and does not do. Meetime does deliver events, and the connector exposes List Webhooks, Create Webhook and Delete Webhook so a flow can subscribe an endpoint of your choosing to CALL and LEAD events. Those are webhook management actions. They create no FlowRunner trigger, because Meetime generates the HMAC signing secret per webhook and returns it only at creation time, so a delivery handler cannot reliably verify a signature without that stored secret. A flow that needs to notice Meetime activity polls List Prospection Activities, List Calls or List Opportunity Feedback on a schedule. ### Without FlowRunner **Enrollment as copy and paste**: Qualified contacts are moved into a cadence by hand, so the ones that arrive late get enrolled late **Duplicate prospections**: The same person is added to a second cadence because nobody checked the first one was still running **Activity reported by export**: Calls, demos and handoffs reach a dashboard when someone remembers to pull the CSV ### With FlowRunner **Enrollment on the same cadence as qualification**: Add Lead to Cadence runs as part of the qualifying flow rather than as a separate afternoon task **Running prospections checked first**: List Prospections and List Leads are read before enrollment, not after a duplicate has been dialled **Activity readable on a schedule**: List Calls, List Demos and List Opportunity Feedback keep the reporting layer current without an export ## Use Case Scenarios ### Qualified contacts into the right fluxo A marketing segment in [Brevo](https://flowrunner.ai/integrations/brevo) or a scoring step upstream produces contacts that meet the qualification bar. The agent reads List Custom Fields to resolve the PICKLIST option identifiers Meetime expects (the option ids, not their text labels), reads List Cadences to pick the cadence matching the segment and to retrieve that cadence's token. It then checks List Leads and List Prospections so nobody already inside a running prospection gets enrolled twice. Then it enrolls with Add Lead to Cadence. The mapping work that used to make bulk enrollment error-prone happens in the flow, every time, at the same standard. ### Prospecting activity into the reporting layer On a schedule the agent pulls List Prospections, List Prospection Activities, List Calls and List Demos with date-range filters covering the last window, resolves user names with List Users and loss reasons with List Loss Reasons, and appends the joined rows to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) or a warehouse table. When a call is worth a human read it fetches Get Call Summary and Get Call Recording and posts the summary and recording link to the sales channel in [Slack](https://flowrunner.ai/integrations/slack). The dashboard stops depending on somebody exporting a CSV on Friday. ### A lead correction that does not erase the record Enrichment elsewhere in the flow finds a corrected job title for a lead already in a cadence. Because Edit Lead is a full replacement, the agent does not send just the title. It reads the lead with Get Lead, merges the correction into the complete editable field set including the customFields object and the phones array, and writes the whole record back. Where the merge would drop a field it cannot read back, it stops and asks rather than writing. This is the mundane version of the [digital andon cord](https://flowrunner.ai/concepts/digital-andon-cord): the flow halts on an ambiguity instead of quietly destroying data it did not understand. ## Human-in-Loop Highlight The gate on Meetime is Add Lead to Cadence, and what makes it a real gate is an operation that is missing rather than one that is present. This connector can enroll a lead in a cadence. It has no action that removes one. Combined with startImmediately defaulting to true when omitted, a bad enrollment means real outreach going to real people under a named SDR's identity, starting now, with no route back through the API. So the agent does the assembly and stops before the enrollment. It posts to the SDR manager: "34 leads from the \[segment\] qualify for cadence \[name\], owned by \[owner\]. Six are already in a running prospection and have been excluded. The first step of this cadence is \[activity template\], and startImmediately is on, so the first touch goes out on enrollment. Confirm the cadence and the remaining 28, or hold." The manager approves, adjusts the list, or picks a different fluxo. Only then does the agent call Add Lead to Cadence with the cadence token. Reading, deduplicating and field mapping run unattended. The first message to a stranger does 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 20 actions ### Leads 3 - **List Leads** Returns a page of leads from the Meetime account. Supports pagination (limit up to 100, default 100, and a page number via start) and filtering by id, email, creation date range, update date range, and whether deleted leads are included. Each lead includes contact fields, phones, custom fields, and its current prospection id. - **Get Lead** Retrieves a single lead by its id. Meetime has no dedicated get-by-id path, so this queries the leads list filtered by the id and returns the standard list envelope. The matching lead is the first item in the data array, or the array is empty when no lead matches. - **Edit Lead** Updates a lead by its id. This operation performs a complete replacement of the lead data: any editable field omitted from the request has its current value erased. Provide every field you want to keep. Custom fields are sent inside the customFields object, and phones is an array of objects with label, phone, and lastUsage. ### Cadences and Prospecting 7 - **Add Lead to Cadence** Adds a lead to a cadence and starts a new prospection for that lead. Authentication for this endpoint uses the cadence token query parameter, not the account API token. When startImmediately is omitted it defaults to true. PICKLIST custom fields must be sent using their option identifiers, not their text labels. This is the action routed for human sign-off. - **List Cadences** Returns a page of cadences (fluxos) configured in the account. Each cadence includes its id, name, its own token used to add leads to it, execution type, focus, priority, owner, and whether it is currently executing. Supports filtering by id, owner, execution type, focus, and priority. - **List Activity Templates** Returns a page of activity templates used to build cadence steps. Each template includes its id, name, activity type, instruction, social network when applicable, and email template. Read it to know what a cadence will actually send. - **List Prospections** Returns a page of prospections, a lead's journey through a cadence. Supports pagination and filtering by id, user, lead, cadence, lead base, status, and multiple date ranges. Set Include Deleted to also return deleted prospections. - **List Prospection Activities** Returns a page of prospection activities, the individual steps executed against leads. Supports filtering by id, assigned user, executor, prospection, lead, status, type, scope, and date ranges. This is the operation a scheduled flow polls to detect movement. - **List Loss Reasons** Returns the loss reasons (motivos de perda) configured in the account, each with its id and name. - **List Opportunity Feedback** Returns a page of opportunity feedbacks, the SDR-to-sales handoffs and their outcomes. Each item includes cadence, lead, SDR, salesman, meeting dates, outcome, whether feedback was replied, and won date. ### Calls and Demos 4 - **List Calls** Returns a page of calls (ligacoes) logged in the account. Each call includes participants, phones, duration, status, output, type, price, and notes. Supports filtering by id, user, receiver type, output, status, call type, importance, and start or update date ranges. Read only. - **Get Call Summary** Returns the AI-generated summary for a single call, identified by its id. - **Get Call Recording** Returns the recording URL for a single call, identified by its id. - **List Demos** Returns a page of demos (product demonstrations) logged in the account. Each demo includes participants, schedule and start times, type, and importance. Supports filtering by id, user, scheduler, demo type, importance, and date ranges. Read only. ### Account 3 - **Get Account Info** Returns information about the Meetime account, including its id, name, status, enabled modules, add-ons, integrations, and creation date. - **List Users** Returns a page of users in the account, including id, name, email, role, active state, modules, and team. Supports filtering by id, module, role, active state, email, and deletion date range. - **List Custom Fields** Returns the lead custom fields defined in the account. Each field includes its id, name, field key, data type, and for PICKLIST fields the list of options with their ids and labels. Read this before any enrollment that sets a selection field. ### Webhooks 3 - **List Webhooks** Returns the webhooks configured in the account. Each webhook includes its id, target URL, subscribed events, enabled state, signing secret, and timestamps. - **Create Webhook** Creates a webhook that delivers the selected events to a target URL of your choosing. Meetime signs each delivery with HMAC-SHA256 using a secret returned in the response, and retries failed deliveries for up to 3 days. This subscribes an external endpoint and does not create a FlowRunner trigger. - **Delete Webhook** Deletes a webhook by its id. The webhook stops receiving deliveries. ## Frequently Asked Questions ### What can FlowRunner do with Meetime? FlowRunner agents can run List Leads, Get Lead, and Edit Lead in Meetime, plus 17 more actions. ### Does connecting Meetime to FlowRunner require OAuth? No. Meetime connects to FlowRunner with an API key, no OAuth flow required. ### Can Meetime trigger a FlowRunner workflow automatically? Meetime doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Meetime?** This integration exposes Meetime 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/meetime. Site index: https://flowrunner.ai/llms.txt