iPaaS.com

Showing 25 of 233 from the live probe.

• Check My Permissions

  Find out what THIS credential is actually allowed to do. Read-only. It asks the authoritative endpoint first (GET /sso/v2/Auth/Permissions, 'permissions for the current user') and, when that cannot answer, falls back to PROBING one cheap read per permission area. The result says which method answered, so you know whether you are reading a declaration or an observation. As of 2026-08-20 the authoritative route does not work for API-key auth: it is user-scoped, and an API key has no user, so it re

• Get Active Tenant

  Report which iPaaS.com company (tenant) this MCP connection is bound to. The connection uses one API key, which is bound to a single company for its whole life; to work in a different company, connect with that company's API key. Call this before a write to confirm you are in the intended company. Read-only.

• Match Data Type

  Match a third-party system's vocabulary to an iPaaS.com data type. Given a foreign term (e.g. 'Stock Level', 'Contact', 'Bundle', 'Tender'), return the iPaaS.com data type(s) it corresponds to, each with its description, the other names it goes by, and the reference doc to open next. Use this FIRST when a user or system uses terminology you're unsure maps to which iPaaS type. Read-only. One term can match MORE THAN ONE type (e.g. 'Account' = B2C Customer or B2B Customer Company; 'Order' = a Tran

• Get Data Model

  Get an iPaaS.com data-model reference doc — topology (parent/child), mapping collection types, default translation types, custom-field gaps, and sync-order notes for a data type. Read-only. Field names/types/required flags are NOT here (those come from Swagger); this is the modeling/discovery layer. Pass a model name or path (e.g. 'product', 'inventory', 'customer', 'transactions/transaction'). With no argument, returns the data-type catalog (the index of every type + aliases) — a good place to

• List Platform Categories

  List the categories of systems iPaaS.com integrates with (eCommerce, ERP, PIM, POS/Retail, 3PL/Fulfillment, CRM, …) — each with a one-line description. Use it to understand what CLASS a given system belongs to and what it typically does; then get_platform_category for the full profile (typical flows, example systems, what's in/out of scope). Read-only.

• Get Platform Category

  Get the full profile of a system category (e.g. 'ecommerce', 'erp', 'pos-retail', 'pim', '3pl-fulfillment') — what it is, the systems it's often integrated with, example platforms, what's typically NOT included, and the common data flows (to/from iPaaS.com). Use it to understand a system you're integrating and what data should flow. Read-only. Use list_platform_categories for the valid names.

• Get Api Contract

  Read the iPaaS.com API's OWN swagger for a service — the documented request model, parameters, responses and per-field notes. Read-only. USE THIS WHEN AN ENDPOINT DOES NOT BEHAVE AS EXPECTED, before probing it: a 400 you do not understand, a member you are unsure exists, a field whose meaning when OMITTED matters, an unexplained 202, or a response shape that surprised you. The descriptions routinely carry things no amount of trial and error would reveal — which members are required, what omittin

• Parse Ipaas Url

  Decode a link from the iPaaS.com web app: say which screen it is, what each id in the path identifies, and which MCP tools open the same thing. Read-only, no API call. Use it whenever someone pastes an app URL instead of guessing which number is which — the path segments are unlabelled, and a subscription id, a system id and a mapping collection id all look the same. Accepts a full URL or just the path. The host tells you which environment the link is from (dev/qa/staging/prod); if it differs fr

• Build Ipaas Url

  Build a link to a record, error or config screen in the iPaaS.com web app — the reverse of parse_ipaas_url. Read-only, no API call. Use it to hand the user a clickable link instead of a bare id: after a sync, when reporting an error, or when pointing at the mapping collection you just changed. The portal host follows the environment this connection targets (production → portal.ipaas.com, staging → stagingportal.ipaas.com), so a staging record never gets a production link. QA has no known portal

• Find Help Articles

  Find the iPaaS.com help-centre articles for an integration, an error message, or a topic — and then READ them. Read-only; returns links, not summaries, so you can quote the source. USE THIS BY DEFAULT WHEN DEBUGGING, before proposing any fix. The help centre publishes per-integration pages that answer most integration questions outright: '<X> Error Messages' (the exact failure texts and what they mean), '<X> Known Limitations' (what the connector deliberately does not do), '<X> Connections and S

• List Employees

  List or search employees for the authenticated iPaaS.com company. Read-only. By default returns a compact summary per employee (id, name, email). Set `detailed` to true for full records including addresses and custom fields. To find someone by name or email, pass `search` — do not page through the whole list looking for them. Returns only active employees. Deleted ones are excluded from every result including searches, unless you pass status='deleted'. IMPORTANT: `search`, `modifiedSince`, and s

• Get Employee

  Get one full employee record by their iPaaS.com employee id, including addresses, custom fields and external ids. Read-only. If you only know a name or email, call list_employees with `search` first. Deleted employees return 404 here — reach them via list_employees with status='deleted' instead.

• List Timesheets

  List timesheets for the authenticated iPaaS.com company. Read-only. Timesheets are a company-wide collection, NOT nested under an employee — to get one person's timesheets, pass `employeeId`. Returns only active timesheets unless you pass status='deleted'. IMPORTANT: `employeeId`, `minTotalHours`, `modifiedSince`, and status='deleted' are mutually exclusive. The API applies one match action across every filter field, so combining them yields wrong results. Pick one per call and narrow the rest y

• Get Timesheet

  Get one full timesheet by its iPaaS.com timesheet id. Read-only. The response already includes every time entry, custom field and external id inline, so there is no need to fetch entries separately afterwards. Use list_timesheets to find ids.

• Get Employee Address

  Get one employee address by its id, including its custom fields and external ids. Read-only. Usually unnecessary: addresses already arrive inline on the employee record from get_employee and from list_employees with detailed=true. Reach for this when lookup_employee_ipaas_id hands you an address id and you have nothing else. Address ids are composite, `<employeeId>|<addressId>` (e.g. `208|219`). The bare address number is rejected. The leading segment is the employee id, so you can also just cal

• Lookup Employee External Id

  Translate an iPaaS.com record id into the id the same record has in an external system. Read-only. Returns the bare external id as plain text. Use this when asked what an employee or timesheet is called in another system. `systemId` identifies that external system and is required — a correct record id with the wrong systemId returns 'not found'.

• Lookup Employee Ipaas Id

  Translate an external system's record id into the iPaaS.com id for the same record — the reverse of lookup_employee_external_id. Read-only. Returns just the iPaaS id, which you can then pass to get_employee, get_timesheet, get_employee_address or get_timesheet_entry depending on recordType. One systemId can hold mappings for several record types, so recordType is what disambiguates them — the same systemId with the wrong recordType reports not found rather than returning the wrong record. Note:

• Get Timesheet Entry

  Get a single time entry by its id. Read-only. Prefer get_timesheet or list_timesheets — both already return all of a timesheet's entries inline. This is only useful when you have an entry id on its own and not the timesheet around it. Entry ids are composite, formatted `<timesheetId>|<entryId>` (e.g. `147|127`). The bare entry number alone is rejected with a 400.

• Create Employee Record

  Create a employee record. Dry-run by default; confirm:true to write. Pass the record body in `fields` — learn the shape from the matching read tool. external_ids are dropped unless include_external_ids=true. An employee record's sub-entities take their parent's id: employee_address needs the employee_id; timesheet_entry needs the timesheet_id. All four entities support reactivate.

• Update Employee Record

  Update a employee record by id. Dry-run by default; confirm:true to write. PUT is a FULL REPLACE, so the tool fetches the current record and merges your `fields` over it — pass only what changes. external_ids dropped unless include_external_ids=true.

• Delete Employee Record

  Delete a employee record by id. Soft-delete (reversible via reactivate_employee_record) for entities that support it. Dry-run by default; confirm:true to delete.

• Reactivate Employee Record

  Reactivate (undo the soft-delete of) a employee record by id. Dry-run by default; confirm:true to reactivate.

• Get Employee Record

  Get any employee record/sub-record by id — the generic by-id resolver for sub-records that lack a dedicated read tool. Read-only. Prefer dedicated get_* tools for the main entities; sub-records also arrive inline on the parent.

• Set Employee External Id

  Create or update the mapping between an iPaaS.com employee record and the id it has in an external system, so lookups resolve between them. Use this to establish or correct a cross-system id link. This WRITES an external id (ordinary record writes never do that implicitly). Dry-run by default; confirm:true to apply. iPaaS has no rollback — keep the change_log.

• Delete Employee External Id

  Remove the mapping between an iPaaS.com employee record and its external-system id. Only the id link is removed — the records themselves are untouched. Dry-run by default; confirm:true to delete.