← Back to connectors

FieldPulse connector for Okou

Read FieldPulse service records by ID, service locations, accounting classes, and API version metadata. Related-record expansions and write operations are intentionally excluded.

Sales & operations · API Key

Use FieldPulse in Okou

Read FieldPulse field-service records by known ID, list service locations, inspect QuickBooks accounting classes, or check API version metadata.

Once connected, supported FieldPulse actions can become steps in a reusable workflow alongside the other services your team uses. Run the workflow once, on a schedule, or when an event starts it.

What you can do with FieldPulse

  • Read specific customer and operational records by known ID, and list service locations. Includes private account-scoped data, but no related-record expansions or write operations.
  • Read QuickBooks accounting-class metadata for jobs, estimates, and invoices; no transaction records or public links.
  • Read reported, latest, and deprecated API version metadata.

How the FieldPulse connector works

A connected service becomes one permissioned step in the work you hand off.

  1. 1

    Connect FieldPulse

    Choose API Key.

  2. 2

    Choose the work

    Use only the supported actions your workflow needs.

  3. 3

    Run it your way

    Start it once, schedule it, or attach an event trigger.

Connect FieldPulse securely

Use the connection method that fits your account and grant only the access the workflow needs.

  • API Key

Connector access is controlled per service and per action, so a workflow does not need broader access than the work you ask it to do.

What FieldPulse covers

The topics this connector's published operations touch.

  • field service management
  • service records
  • locations
  • read only

FieldPulse connector questions

What can Okou do with FieldPulse?
Read FieldPulse service records by ID, service locations, accounting classes, and API version metadata. Related-record expansions and write operations are intentionally excluded. Documented actions include: Read specific customer and operational records by known ID, and list service locations. Includes private account-scoped data, but no related-record expansions or write operations. Read QuickBooks accounting-class metadata for jobs, estimates, and invoices; no transaction records or public links.
How do I connect FieldPulse to Okou?
Connect FieldPulse using API Key. The connection controls which supported actions a workflow can use.
Can FieldPulse run in an automated workflow?
Yes. After it is connected, supported FieldPulse actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.

More sales & operations connectors

Explore other connectors in the same product category.