--- title: "Teamgate Integration" description: "Connect AI agents to Teamgate, a sales CRM for small and medium businesses. Agents create leads and move them into people and companies, open deals, log activities, and read the product catalog a deal quotes from." url: https://flowrunner.ai/integrations/teamgate-crm date_modified: 2026-08-11T09:36:14-07:00 --- # Teamgate [CRM](https://flowrunner.ai/integrations/category/crm-sales) Connect AI agents to Teamgate, a sales CRM for small and medium businesses. Agents create leads and move them into people and companies, open deals, log activities, and read the product catalog a deal quotes from. 26 actions · Custom auth · available [Teamgate website](https://teamgate.com/) · [Platform Documentation](https://developers.teamgate.com/) · Capability data verified 2026-08-11 1. A web form, a chat submission, or a scheduled read of an inbound source starts the run 2. Create Lead captures the prospect with its source and owner before anything is qualified 3. Get Lead reads back the captured record with the fields the form supplied 4. Get Companies and Get People resolve whether this prospect already exists as a customer record 5. Create Company and Create Person write the qualified prospect into the customer side of the CRM 6. The new records are read back and compared against the lead they were built from 7. A person decides whether Delete Lead may remove the original, since Teamgate has no convert action ## What This Integration Enables Teamgate is a sales CRM for small and medium businesses, and it keeps a distinction that larger platforms tend to blur: a lead is a separate object from a person and a company, not a status flag on one. That is the design decision this connector has to respect. Leads, people, companies, deals, and activities each carry the full create, read, update, and delete lifecycle, Get Pipelines exposes pipelines and their stage IDs for deal staging, and Get Products reads the product catalogue. What the connector does not offer is a conversion action, because Teamgate's model does not hand one over here. Qualifying a lead means creating the person and the company yourself, carrying across what matters, and then deciding what happens to the original lead record. That is a genuine sequence of separate writes rather than one atomic operation, and designing around it honestly is more useful than pretending otherwise. The mechanics are straightforward once a few things are known. All calls target the v4 API, and authentication sends two headers on every request: `X-App-Key` for your application key, requested under Settings, Additional features, External App, New API Key request, and `X-Auth-Token` for your personal authorization token, found under My Profile, Integrations, API access. The token identifies the acting user, so any record created without an explicit owner is attributed to whoever's token is in configuration. List actions page with `limit` and `offset` rather than page numbers, this connector applies a default limit of 25, and the response `count` reports how many entities came back in that page. Sorting uses Teamgate's `order[field]=asc|desc` syntax on name, created time, or updated time. Deal status maps readable labels onto Teamgate's wire values, where Open maps to `active` and Won, Lost, and Postponed map to their lowercase equivalents. Customer Status runs Non Customer, Past Customer, Customer as 0, 1, 2, and Prospect Status runs Non Prospect, Lost Prospect, Prospect on the same scale. Create Activity supports Task, Call, Appointment, and Note, where the completion status of Incomplete, Successful, or Unsuccessful applies to tasks and calls only, and a note stores its Description as the note content. Deals reference a stage by ID, so Get Pipelines runs before any deal is created or moved. Products are read only through this connector: Get Products retrieves the catalogue, and there is no action here that attaches a product to a deal or writes to the catalogue. This connector ships no triggers, so change detection is a scheduled Get Leads or Get Deals sorted by updated time descending, with the flow carrying its own high-water mark between runs. Delete Lead, Delete Person, Delete Company, Delete Deal, and Delete Activity are permanent. ### Without FlowRunner **Qualification is a copy and paste job**: A rep retypes a lead into a company and a person, and the lead source is lost in the retyping **Stage IDs are guessed**: A deal is written to a stage from the wrong pipeline and disappears from the report it belonged in **Activity happens away from the record**: Calls and appointments occur and the deal shows no history of anyone working it ### With FlowRunner **Capture is immediate and attributed**: Create Lead writes the prospect with its source and owner at the moment the form is submitted **Stages are resolved before they are set**: Get Pipelines returns pipelines and their stage IDs, so a deal is staged against a real ID **History lands on the record**: Create Activity writes tasks, calls, appointments, and notes against the lead, company, or deal ## Use Case Scenarios ### An inbound enquiry captured with its source intact A demo request or a chat conversation ends with contact details. The agent calls Create Lead immediately, writing the name, company, email, phone, source, and owner, because the value of a lead record is highest at the moment of capture and decays as soon as someone starts retyping it. Where routing rules assign an owner, that owner is set explicitly rather than left to default to the token holder in configuration. Create Activity then writes a Task against the lead with the first follow-up and a due date, so the prospect arrives in the CRM already attached to an action rather than to an intention. The rep gets a message in [Slack](https://flowrunner.ai/integrations/slack) naming the lead, its source, and the task waiting on them. ### A deal staged against a pipeline that actually exists A qualified opportunity is ready to open. The agent calls Get Pipelines first and resolves the target stage ID from the named pipeline, which sounds like a formality until you consider what happens if it is skipped: a stage ID copied from another pipeline produces a deal that saves without error and then goes missing from the forecast it was meant to appear in. With a real stage ID in hand, Create Deal opens the opportunity against the resolved company and person with its amount and owner. Get Products reads the catalogue so the agent can name the products discussed in the deal description and in the follow-up, though attaching products to the deal itself is done in Teamgate rather than through this connector. As the deal progresses, Update Deal moves it between stages and sets its status to Won, Lost, or Postponed. ### A pipeline review assembled from reads alone On a schedule the agent calls Get Deals with `limit` and `offset` paging and Teamgate's `order[updated]=desc` sorting, reading `count` on each page rather than assuming a page is the whole set. For each open deal it calls Get Company and Get Person for the account and buyer, and Get Activities to see whether any task, call, or appointment is actually scheduled against it. The joined view separates the deals that are being worked from the deals that are merely open, which is a distinction a stage name alone will never make. The result appends to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and a per-owner summary goes to [Microsoft Teams](https://flowrunner.ai/integrations/microsoft-teams). Nothing is written back, so it runs every morning without needing anyone's permission. ## Human-in-Loop Highlight The gate belongs on Delete Lead, and it belongs there because of what Teamgate does not provide. There is no convert action in this connector. Qualifying a lead is three separate writes: Create Company for the account, Create Person for the buyer, and then a decision about the lead record that is now a duplicate of both. Leaving it in place clutters the lead queue and makes the same prospect appear twice in reporting. Removing it is permanent, and the lead record is the only place that holds where the prospect came from in the form Teamgate captured it, along with the lead status and the source attribution that marketing measures its own spend against. The failure that actually happens is partial. Create Company succeeds, Create Person fails validation on a missing field, the flow proceeds to tidy up, and Delete Lead destroys the source record for a prospect who now exists as a company with no contact attached to it. There is no undo, and the original enquiry is gone. So the agent completes the qualification and then stops. It calls Get Company and Get Person to read back what it just created, compares those records field by field against the lead they came from, and posts to the sales operations owner: "31 leads qualified this morning. 27 produced a matching Company and Person with the source, owner, and phone carried across intact. 4 did not: 2 have a Company but no Person because the enquiry carried no last name, 1 matched an existing Company under a slightly different spelling and may now be a duplicate account, and 1 has no source value on either new record. Delete Lead is permanent and the lead is the only record holding the original source attribution. Delete the 27, delete none, or delete only the ones where every field was carried across?" The operations owner answers once, the agent applies that rule, and Delete Lead runs only where a person confirmed the qualification actually landed. This is the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) moment on a CRM that treats leads as real objects rather than as a flag, because an agent can prove which qualifications completed cleanly and only a person can decide whether an imperfect one is worth destroying the original for. 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 26 actions ### Leads 5 - **Create Lead** Captures a prospect with name, company, contact details, source, and owner. Records created without an explicit owner are attributed to the user whose auth token is in configuration. - **Get Leads** Returns leads with \`limit\` and \`offset\` paging and \`order\[field\]=asc|desc\` sorting on name, created time, or updated time. This is the scheduled read that substitutes for the events this connector does not receive. - **Get Lead** Retrieves a single lead with its status, source, and owner. - **Update Lead** Updates a lead, including its status and owner as qualification progresses. - **Delete Lead** Permanently removes a lead. The lead record holds the original source attribution, and the delete cannot be undone. ### People 5 - **Create Person** Creates a contact. Accepts a single primary work email and phone for convenience, which Teamgate stores as typed contact entries. Customer Status runs Non Customer, Past Customer, Customer and Prospect Status runs Non Prospect, Lost Prospect, Prospect. - **Get People** Returns contacts with paging and sorting, used to resolve whether a prospect already exists before creating another. - **Get Person** Retrieves a single contact with its statuses and linked company. - **Update Person** Updates a contact's details or statuses. - **Delete Person** Permanently removes a contact and cannot be undone. ### Companies 5 - **Create Company** Creates an account record with its primary contact details and statuses. - **Get Companies** Returns companies with paging and sorting. The deduplication read that runs before a qualification writes a new account. - **Get Company** Retrieves a single company with its details. - **Update Company** Updates a company, used to keep an account current from the system that genuinely owns the field. - **Delete Company** Permanently removes a company and cannot be undone. ### Deals 6 - **Create Deal** Opens a deal against a company and person. Deals reference a stage by ID, so Get Pipelines runs first. - **Get Deals** Returns deals with \`limit\` and \`offset\` paging and sorting, with \`count\` reporting how many came back in the page. - **Get Deal** Retrieves a single deal with its amount, owner, stage, and status. - **Update Deal** Updates a deal, including moving it between stages and setting status to Open, Won, Lost, or Postponed, where Open travels as \`active\`. - **Delete Deal** Permanently removes a deal and cannot be undone. - **Get Pipelines** Returns pipelines and their stage IDs. The lookup that has to run before any deal is created or moved, since a stage ID from the wrong pipeline saves without erroring. ### Activities 4 - **Create Activity** Writes a Task, Call, Appointment, or Note against a lead, company, person, or deal. Completion status of Incomplete, Successful, or Unsuccessful applies to tasks and calls only, and a note stores its Description as the note content. - **Get Activities** Returns activities with paging, used to see whether a deal is actually being worked rather than merely open. - **Get Activity** Retrieves a single activity with its type and completion status. - **Delete Activity** Permanently removes an activity and cannot be undone. ### Products 1 - **Get Products** Reads the product catalogue. Products are read only through this connector: there is no action here that creates a catalogue entry or attaches a product to a deal. ## Frequently Asked Questions ### What can FlowRunner do with Teamgate? FlowRunner agents can run Create Lead, Get Leads, and Get Lead in Teamgate, plus 23 more actions. ### Does connecting Teamgate to FlowRunner require OAuth? Teamgate uses a custom authentication method to connect to FlowRunner. ### Can Teamgate trigger a FlowRunner workflow automatically? Teamgate doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Teamgate?** This integration exposes Teamgate 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/teamgate-crm. Site index: https://flowrunner.ai/llms.txt