> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/apptivo.md).

# Apptivo

Connect Apptivo CRM data to Google Sheets, BigQuery, or Snowflake via Coupler.io. Sync customers, contacts, leads, opportunities, and cases without manual expor

Apptivo is a cloud-based CRM and business management platform that helps teams track customers, contacts, leads, opportunities, and support cases in one place. It's a popular choice for small and mid-sized businesses looking for an affordable, all-in-one solution.

Connecting Apptivo to Coupler.io lets you pull your CRM data into the tools you already use for analysis, reporting, and AI-powered workflows — without any manual exporting.

**Why connect Apptivo to Coupler.io?**

* Sync customers, contacts, leads, opportunities, and cases to Google Sheets, Excel, BigQuery, or Looker Studio
* Feed your CRM data into AI tools like ChatGPT, Claude, or Gemini for pipeline analysis or support summarization
* Combine multiple Apptivo entities using Join or Append transformations to build unified reports
* Keep your destination data fresh with scheduled automatic refreshes

## Prerequisites

Before connecting, make sure you have:

* An active Apptivo account with access to the entities you want to export
* An Apptivo **API key** — you can generate this from your Apptivo account settings under **API & Webhooks**
* Admin or sufficient permissions to read the entities you plan to connect

## Quick start

{% hint style="success" %}
Start with the **Opportunities** entity if your goal is sales reporting. It contains deal values, stages, and history — everything you need for a pipeline dashboard.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io and click **Add data flow**. Search for **Apptivo** as your source.
{% endstep %}

{% step %}
**Enter your Apptivo API key.** In the source settings, paste your Apptivo API key. You can find this in Apptivo under **Settings → API & Webhooks → API Key**. If you don't have one yet, generate a new key from that screen.
{% endstep %}

{% step %}
**Select an entity.** Choose the entity you want to import: Customers, Contacts, Cases, Leads, or Opportunities. Each entity is configured as a separate source within your data flow.
{% endstep %}

{% step %}
**Add more sources if needed.** To combine data from multiple entities (e.g., Leads and Opportunities), click **Add source** and repeat the steps above. Use the **Join** or **Append** transformation to merge them.
{% endstep %}

{% step %}
**Choose your destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, Gemini, Perplexity, Cursor, or OpenClaw.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual run. Once it completes successfully, your data will appear in the destination you configured.
{% endstep %}
{% endstepper %}

## Available entities

| Entity        | Description                                                |
| ------------- | ---------------------------------------------------------- |
| Customers     | Companies or organizations that are your clients           |
| Contacts      | Individual people linked to customers or standalone        |
| Leads         | Unqualified prospects at the top of your sales funnel      |
| Opportunities | Qualified deals tracked through the sales pipeline         |
| Cases         | Support tickets and issues with full communication history |

## Apptivo data overview

Apptivo exposes five core CRM entities through Coupler.io. Each entity maps to a key part of your business workflow — from prospecting to customer support.

## Entities at a glance

| Entity        | Best used for                                 |
| ------------- | --------------------------------------------- |
| Customers     | Account-level reporting, revenue attribution  |
| Contacts      | People-level data, communication tracking     |
| Leads         | Top-of-funnel analysis, lead source reporting |
| Opportunities | Pipeline reporting, win/loss analysis         |
| Cases         | Support volume, resolution time, SLA tracking |

## Customers

#### Key fields

| Field         | Description                                            |
| ------------- | ------------------------------------------------------ |
| Customer ID   | Unique identifier for the customer record              |
| Customer Name | Name of the company or organization                    |
| Customer Type | Classification of the customer (e.g., client, partner) |
| Status        | Active, inactive, or other custom status               |
| Industry      | Industry sector of the customer                        |
| Owner         | Apptivo user assigned to this customer                 |
| Created Date  | Date the record was created                            |
| Last Updated  | Date the record was last modified                      |

## Contacts

#### Key fields

| Field                  | Description                                     |
| ---------------------- | ----------------------------------------------- |
| Contact ID             | Unique identifier for the contact record        |
| First Name / Last Name | Individual's name                               |
| Email                  | Primary email address                           |
| Phone                  | Primary phone number                            |
| Linked Customer        | Customer record this contact is associated with |
| Job Title              | Contact's role or title                         |
| Owner                  | Apptivo user assigned to this contact           |
| Created Date           | Date the record was created                     |

## Leads

#### Key fields

| Field           | Description                                                 |
| --------------- | ----------------------------------------------------------- |
| Lead ID         | Unique identifier for the lead                              |
| Lead Name       | Name of the prospect                                        |
| Lead Source     | Channel or campaign that generated the lead                 |
| Status          | Current stage of the lead (e.g., New, Contacted, Qualified) |
| Estimated Value | Potential deal value                                        |
| Owner           | Apptivo user responsible for the lead                       |
| Created Date    | Date the lead was created                                   |

## Opportunities

#### Key fields

| Field            | Description                                                      |
| ---------------- | ---------------------------------------------------------------- |
| Opportunity ID   | Unique identifier for the opportunity                            |
| Opportunity Name | Name or title of the deal                                        |
| Stage            | Current pipeline stage (e.g., Proposal, Negotiation, Closed Won) |
| Probability      | Likelihood of closing, as a percentage                           |
| Expected Revenue | Projected deal value                                             |
| Close Date       | Expected or actual close date                                    |
| Linked Customer  | Associated customer record                                       |
| Owner            | Apptivo user managing the deal                                   |
| Created Date     | Date the opportunity was created                                 |

## Cases

#### Key fields

| Field           | Description                            |
| --------------- | -------------------------------------- |
| Case ID         | Unique identifier for the support case |
| Case Subject    | Title or summary of the issue          |
| Status          | Open, In Progress, Resolved, Closed    |
| Priority        | Low, Medium, High, or Urgent           |
| Linked Customer | Customer the case belongs to           |
| Linked Contact  | Individual who raised the case         |
| Assigned To     | Support agent handling the case        |
| Created Date    | Date the case was opened               |
| Resolved Date   | Date the case was resolved             |

## Common field combinations

* **Pipeline report:** Opportunities — Stage + Expected Revenue + Close Date + Owner
* **Lead conversion analysis:** Leads — Lead Source + Status + Estimated Value + Created Date
* **Support workload:** Cases — Status + Priority + Assigned To + Created Date
* **Account health view:** Join Customers + Cases to see open issues per account
* **Full contact picture:** Join Contacts + Customers to enrich contact records with company data

## Use cases by role

{% tabs %}
{% tab title="Sales teams" %}

* Track your opportunity pipeline by stage, owner, and close date in a live Google Sheets or Looker Studio dashboard
* Use the Leads entity to measure which sources drive the most qualified prospects
* Join Leads and Opportunities to analyze conversion rates from prospect to qualified deal
* Feed opportunity data into ChatGPT or Claude to generate deal summaries or forecast commentary
  {% endtab %}

{% tab title="Customer success" %}

* Export Cases to track open support tickets, average resolution time, and case volume by customer
* Join Cases and Customers to identify which accounts generate the most support load
* Use Aggregate transformation on Cases to count open vs. closed tickets per assignee
* Send case data to an AI destination like Gemini for automated issue categorization
  {% endtab %}

{% tab title="RevOps & analysts" %}

* Combine all five entities in a single data flow using Append or Join to build a unified CRM dataset in BigQuery
* Use the Customers entity as a master table and join Opportunities, Cases, and Contacts to it for full account-level reporting
* Schedule regular refreshes to keep dashboards current without manual exports from Apptivo
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Apptivo uses custom fields extensively — these will appear as additional columns in your export depending on your account configuration
* Field names may reflect your Apptivo customizations, so column headers in Coupler.io might differ from the default labels shown above
* Deleted records are not returned by the API — only active records are included in exports
* Apptivo's API returns data in pages; Coupler.io handles pagination automatically

## Apptivo common issues

### Connection issues

<details>

<summary>Invalid API key error when connecting</summary>

Double-check that you've copied the full API key from Apptivo without any leading or trailing spaces. In Apptivo, go to **Settings → API & Webhooks → API Key** to view or regenerate your key. If you recently regenerated a key, the old one is immediately invalidated — update Coupler.io with the new value.

</details>

<details>

<summary>Data flow fails immediately after setup</summary>

This can happen if your Apptivo user account doesn't have API access enabled. API access may need to be turned on at the plan or admin level. Check with your Apptivo administrator to confirm that API access is active for your account.

</details>

### Missing data

<details>

<summary>Some records are missing from the export</summary>

Apptivo's API only returns active, non-deleted records. If a customer, lead, or case was deleted in Apptivo, it won't appear in Coupler.io. Also check whether the records are assigned to a different user — depending on your Apptivo permissions, you may only see records you own or have access to.

</details>

<details>

<summary>Custom fields are not appearing in the output</summary>

Custom fields are included in the export, but their column names will match the labels set in your Apptivo account. If a custom field was recently added in Apptivo, try running the data flow again — Coupler.io will pick up new fields on the next run.

</details>

### Permission errors

<details>

<summary>403 Forbidden or "Access denied" error</summary>

This typically means the API key belongs to a user who doesn't have read access to the entity you're trying to export. For example, if your user role restricts access to Opportunities, the API will return a 403. Ask your Apptivo admin to adjust permissions for that user, or use an API key from an admin account.

</details>

### Data discrepancies

<details>

<summary>Record counts in Coupler.io don't match Apptivo</summary>

Apptivo's UI counts may include archived or filtered records that the API excludes. Specifically, the API typically excludes deleted records and may apply default filters (e.g., only returning records in an "active" status). Compare with an unfiltered Apptivo list view rather than a saved filtered view.

</details>

<details>

<summary>Field values look different from what I see in Apptivo</summary>

Some Apptivo fields store an internal ID or code rather than the display label. For example, a status field might export as a numeric code instead of "Closed Won". This is an Apptivo API behavior. You can use a lookup table or Coupler.io's transformation features to map these codes to readable labels.

</details>

### Rate limits

<details>

<summary>Data flow is slow or times out on large entities</summary>

Apptivo enforces API rate limits that vary by plan. If you have a large number of records (thousands of leads or cases), the export may take longer as Coupler.io pages through the results. Avoid running multiple data flows against Apptivo simultaneously to reduce the chance of hitting rate limits.

</details>

## Apptivo FAQ

<details>

<summary>Where do I find my Apptivo API key?</summary>

Log in to Apptivo and go to **Settings → API & Webhooks → API Key**. If no key exists yet, you can generate one from that screen. Copy the full key and paste it into the Coupler.io source settings when setting up your data flow.

</details>

<details>

<summary>Can I connect multiple Apptivo accounts to Coupler.io?</summary>

Yes. Each Apptivo account has its own API key. You can create separate data flows for each account and use the Append transformation to combine data from both into a single destination. This is useful if your business operates multiple Apptivo instances.

</details>

<details>

<summary>Can I pull all five entities into one destination sheet or table?</summary>

Each entity has a different structure, so appending all five into a single flat table doesn't typically make sense. Instead, set up each entity as its own source and use the Join transformation to link related entities (e.g., Opportunities joined to Customers). For a data warehouse like BigQuery, you can load each entity into its own table and relate them using SQL.

</details>

<details>

<summary>Does Coupler.io export all records or just recent ones?</summary>

Coupler.io retrieves all available records from Apptivo by default — there's no built-in date filter at the source level. If you only want recent records, you can filter the data after it lands in your destination (e.g., using a filter in Google Sheets or a WHERE clause in BigQuery).

</details>

<details>

<summary>Why are some Apptivo fields showing codes or IDs instead of labels?</summary>

Some Apptivo fields store internal identifiers rather than display values. This is an Apptivo API behavior, not a Coupler.io issue. You can create a mapping table in your destination to translate these codes into readable labels.

</details>

<details>

<summary>Can I use Apptivo data with AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Apptivo data — such as open cases or pipeline opportunities — directly to these tools for summarization, analysis, or automated reporting.

</details>

<details>

<summary>How do I track lead-to-opportunity conversion in Coupler.io?</summary>

Add both the Leads and Opportunities entities as sources in the same data flow. Use the Join transformation on a shared field (such as customer name or linked contact) to connect them, then analyze the combined dataset in your destination to measure conversion rates by lead source, owner, or time period.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see the [Data Overview](#apptivo-data-overview) article. If you're running into connection or missing data problems, check [Common Issues](#apptivo-common-issues). For setup recommendations specific to Apptivo, visit [Best Practices](https://docs.coupler.io/sources/category/crm/apptivo/best-practices.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/crm/apptivo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
