Skip to main content
POST
Follow Up Boss and Affinity
Reads contacts and opportunities from Follow Up Boss, and accounts, contacts and opportunities from Affinity.

Follow Up Boss

  • No company object, so account_id is unsupported.
  • Active deals return status: open. Lifecycle flags such as Archived do not establish a won/lost outcome, so won and lost filters are unsupported.
  • Deal currency and update time are unavailable; updated_since is supported for contacts only.
  • Contacts use the primary email and phone when marked, otherwise the first. Contact stage, lead source, assignee and last activity are omitted.
  • source identifies the system and record, not the lead’s acquisition source.

Affinity

  • Opportunities traverse one list per page.
  • name includes the list name followed by the entity name; id is the list-entry id; stage is the list’s Status dropdown text.
  • Explicit Won/Closed Won and Lost/Closed Lost labels map to won and lost. Other labels map to open, never inferred from dropdown rank.
  • Company entries link directly to their account. Other records use the requested associated organization, otherwise the lowest id.
  • Unavailable amounts, currency, owner, close date and update times are null.
  • updated_since is not supported.
Both systems filter within each fetched page; Affinity opportunity searches include list names. Always continue while next_cursor exists, including empty filtered pages. Keep the cursor unchanged; a continuation exceeding the CRM cursor limit returns not_supported.

Both systems

  • Unsupported filters return 400 unsupported_for_system before payment.
  • Tickets and activity return unsupported_read; Follow Up Boss also rejects accounts. CRM writes are not served.
  • Follow Up Boss connects with a sign-in. Affinity connects with an API key, entered in the console or through the connections endpoint.
See CRM inputs and outputs.