Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Field Pulse (BYOK) icon

Field Pulse (BYOK)

Read your FieldPulse field service customers, jobs, estimates, invoices, payments, projects, timesheets, assets and staff with your own API key

Unify Dynamics LLC

Tools10read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderField Pulseunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which customers do I have in FieldPulse?
Tools called
list_customers
Which jobs were created in FieldPulse this month?
Tools called
list_jobs
Show my latest FieldPulse estimates
Tools called
list_estimates
What invoices have I issued in FieldPulse?
Tools called
list_invoices
Which payments did FieldPulse record most recently?
Tools called
list_payments
What projects are open in FieldPulse?
Tools called
list_projects

About

Field Pulse (BYOK) lets an AI assistant read your own Field Pulse data through the Field Pulse API with a key you supply (FieldPulse API key). Read-only: 10 tools (list_customers, list_jobs, list_estimates, list_invoices, list_payments, list_projects, list_timesheets, list_users, list_assets, list_items). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to ywe3crmpll.execute-api.us-east-2.amazonaws.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Field Pulse. Field Pulse and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Field Pulse API (ywe3crmpll.execute-api.us-east-2.amazonaws.com) with a BYOK key; documentation: https://help.fieldpulse.com/api-reference/getting-started. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

10 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data10 tools
  • List customersList customers, optionally searched by text and sorted by email, phone or address.
  • List jobsList jobs, filtered by creation time window or status ids, newest or oldest first.
  • List estimatesList estimates with optional text search and sorting.
  • List invoicesList invoices with optional text search and sorting.
  • List paymentsList payments received, sortable by method, amount or payment date.
  • List projectsList projects with optional text search and sorting.
  • List timesheetsList staff timesheet entries, filtered by user, clock-in or clock-out time, or type.
  • List usersList the company's FieldPulse users (office staff and technicians).
  • List assetsList customer assets (equipment), filtered by status installed, uninstalled or retired.
  • List itemsList the invoice items (price book entries) defined in FieldPulse.

Information

PublisherUnify Dynamics LLC
CategoryMoney & business
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-fieldpulse.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 10 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-fieldpulse.connectorbay.com/mcp
RESTPOST https://byok-fieldpulse.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-fieldpulse.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your FieldPulse API key in the X-Upstream-Key header (get one at help.fieldpulse.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Field Pulse connector: questions and answers

What is the Field Pulse connector?

Field Pulse (BYOK) lets an AI assistant read your own Field Pulse data through the Field Pulse API with a key you supply (FieldPulse API key). It is a hosted MCP server with 10 tools such as List customers, List jobs, List estimates, List invoices, List payments, List projects, published by Unify Dynamics LLC. It is independent and not affiliated with Field Pulse.

How do I connect Field Pulse to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-fieldpulse.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-fieldpulse.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-fieldpulse.json.

Do I need a Field Pulse account or API key?

Yes: this is a bring-your-own-key connector. Create a FieldPulse API key at https://help.fieldpulse.com/api-reference/getting-started and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Field Pulse read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Field Pulse connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Flutterwave (BYOK)

Read your Flutterwave transactions, transfers, refunds, settlements, wallet balances, payment plans and subscriptions with your own secret key

Live · MCP + REST10 tools

Flutterwave Config (BYOK)

Read Flutterwave supported banks and branches, fee quotes, payment plans, bill categories, settlements and chargebacks with your own v3 secret key

Live · MCP + REST12 tools

Financial Modeling Prep Reference (BYOK)

Look up listed companies by name, CIK, CUSIP or ISIN and list exchanges, sectors, industries and countries from Financial Modeling Prep with your own API key

Live · MCP + REST11 tools

Focus NFe (BYOK)

Read your Focus NFe Brazilian fiscal invoice status, received invoices, companies and tax reference tables (NCM, CFOP, CNAE, CEP, municipalities) with your own token

Live · MCP + REST11 tools

ForexRateAPI (BYOK)

Read live, historical, hourly and OHLC foreign exchange rates, conversions and rate changes from ForexRateAPI with your own API key

Live · MCP + REST9 tools

FRED (BYOK)

Read economic data series, observations, releases and categories from the St. Louis Fed FRED database with BYOK

Live · MCP + REST9 tools

Documentation

Back to top

Field Pulse (BYOK) — connector documentation

  • MCP endpoint: https://byok-fieldpulse.connectorbay.com/mcp
  • REST API: POST https://byok-fieldpulse.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-fieldpulse.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Field Pulse FieldPulse API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-fieldpulse.connectorbay.com/health · Tool schemas: https://byok-fieldpulse.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-fieldpulse · agent@connectorbay.com

What Field Pulse (BYOK) is for

Field Pulse (BYOK) lets an AI assistant read your own Field Pulse data through the Field Pulse API with a key you supply (FieldPulse API key). Read-only: 10 tools (list_customers, list_jobs, list_estimates, list_invoices, list_payments, list_projects, list_timesheets, list_users, list_assets, list_items). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to ywe3crmpll.execute-api.us-east-2.amazonaws.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Field Pulse. Field Pulse and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which customers do I have in FieldPulse?"
  • "Which jobs were created in FieldPulse this month?"
  • "Show my latest FieldPulse estimates"
  • "What invoices have I issued in FieldPulse?"
  • "Which payments did FieldPulse record most recently?"
  • "What projects are open in FieldPulse?"

What it does

  • list_customers: List customers, optionally searched by text and sorted by email, phone or address.
  • list_jobs: List jobs, filtered by creation time window or status ids, newest or oldest first.
  • list_estimates: List estimates with optional text search and sorting.
  • list_invoices: List invoices with optional text search and sorting.
  • list_payments: List payments received, sortable by method, amount or payment date.
  • list_projects: List projects with optional text search and sorting.
  • list_timesheets: List staff timesheet entries, filtered by user, clock-in or clock-out time, or type.
  • list_users: List the company's FieldPulse users (office staff and technicians).
  • list_assets: List customer assets (equipment), filtered by status installed, uninstalled or retired.
  • list_items: List the invoice items (price book entries) defined in FieldPulse.

BYOK key

You bring your own Field Pulse FieldPulse API key (https://help.fieldpulse.com/api-reference/getting-started). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to ywe3crmpll.execute-api.us-east-2.amazonaws.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

FieldPulse issues API keys on request: write to support@fieldpulse.com to have one activated. Records are returned as the provider sends them; the API reference does not list record fields.

Data sources

Live from the Field Pulse API (ywe3crmpll.execute-api.us-east-2.amazonaws.com) with a BYOK key; documentation: https://help.fieldpulse.com/api-reference/getting-started. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Field Pulse. Field Pulse and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Field Pulse account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Field Pulse (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Field Pulse (BYOK) is. Field Pulse (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Field Pulse data: Read your FieldPulse field service customers, jobs, estimates, invoices, payments, projects, timesheets, assets and staff with your own API key. You bring your own Field Pulse FieldPulse API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Field Pulse call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to ywe3crmpll.execute-api.us-east-2.amazonaws.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Field Pulse rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Field Pulse receives. The request we make on your behalf, including the key and the arguments, under Field Pulse's own terms and privacy policy. Field Pulse acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Field Pulse gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Field Pulse data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Field Pulse (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Field Pulse at any time to end all access.

Children. Field Pulse (BYOK) is a general-audience service operated by the adult using the assistant, under Field Pulse's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Field Pulse (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Field Pulse (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Field Pulse (BYOK) provides: Read your FieldPulse field service customers, jobs, estimates, invoices, payments, projects, timesheets, assets and staff with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Field Pulse credentials and only access data you are allowed to access. Field Pulse's terms apply to your use of Field Pulse; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Field Pulse. Field Pulse and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Field Pulse returns, lightly trimmed; it may be incomplete, delayed or changed by Field Pulse. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Field Pulse account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Field Pulse's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Field Pulse may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Field Pulse key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Field Pulse takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-fieldpulse

Field Pulse (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Field Pulse (BYOK) never asks for them.

Get Field Pulse (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Field Pulse FieldPulse API key. Create one at https://help.fieldpulse.com/api-reference/getting-started, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Field Pulse. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Field Pulse.