PeopleTide CRM

Integration guide

Let workflows call an approved REST API.

Define named operations against an allowlisted HTTPS system, map typed inputs and outputs, then make those operations available to business tasks.

Updated 13 September 2026 · 9 min read

Connector model

Expose named business operations, not arbitrary requests.

A connector represents one external system. Each operation defines the method, approved path, credential behavior, inputs, response shape, and error outcomes that a workflow may use.

Configuration

Create and test the contract.

  1. 01

    Create the connection

    Open Settings → Integrations → Third-party integrations and add the external HTTPS base URL.

  2. 02

    Store the credential

    Choose the required authentication method and store the secret in the connection rather than a workflow field.

  3. 03

    Define one operation

    Name the action in business language, then set the method, relative path, and allowed inputs.

  4. 04

    Declare outputs

    Map fixed JSON paths to typed result fields. Unmapped response fields are discarded.

  5. 05

    Test errors as well as success

    Exercise invalid input, not found, rate limiting, timeout, and upstream failure behavior.

  6. 06

    Use it in a business task

    Create a task from the connected system, map context fields to inputs, and publish a version.

Example

Prefer “check order status” over “make HTTP request”.

  • Inputs: verified customer phone and order reference.
  • Operation: GET /orders/{reference}/status on the approved host.
  • Outputs: status, expectedDate, and customerMessage.
  • Outcomes: found, not_found, needs_review, and failed.
  • Workflow behavior: answer from mapped outputs or create a ticket when staff judgment is required.