> 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/circa.md).

# Circa

Connect Circa event management CRM to Coupler.io. Pull events, contacts, companies, and relationship data into Google Sheets or BigQuery for unified reporting.

Circa (formerly Simple Circa) is an event management CRM that helps teams plan, track, and manage events, contacts, and companies in one place. You can connect Circa to Coupler.io to pull your event data, contact records, company information, and relationship data into your preferred destination for reporting and analysis.

## Why connect Circa to Coupler.io?

* **Centralize your event data** — combine events, contacts, companies, and their relationships in a single report without manual exports
* **Build custom dashboards** — send Circa data to Google Sheets, Looker Studio, BigQuery, or AI tools like ChatGPT or Gemini for deeper analysis
* **Join related entities** — use Coupler.io's Join transformation to link event contacts with contact records, or company contacts with company details
* **Automate reporting** — keep your reports up to date with scheduled data refreshes instead of manual CSV downloads

## Prerequisites

* An active Circa account
* A Circa API key (available in your Circa account settings)

## Quick start

{% hint style="success" %}
If you're reporting on event performance, start with the **Events** and **Event contacts** entities — join them to see which contacts are associated with each event.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to the Data Flows section, and click **Add data flow**. Search for and select **Circa** as your source.
{% endstep %}

{% step %}
**Enter your Circa API key.** In your Circa account, navigate to your account or developer settings to find your API key. Copy it and paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Select an entity.** Choose which Circa data you want to import — for example, Events, Contacts, or Companies. You can add more sources to the same data flow to pull multiple entities at once.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to define how far back Coupler.io should pull historical data from Circa.
{% endstep %}

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

{% step %}
**Run your data flow.** Click **Run** to execute a manual sync and confirm that your data is flowing correctly before setting up a schedule.
{% endstep %}
{% endstepper %}

## Circa data overview

Circa gives you access to event management and CRM data including events, contacts, companies, teams, and the relationships that connect them. You can also pull custom field definitions to understand how your data is structured.

## Available entities

| Entity           | What it contains                                              |
| ---------------- | ------------------------------------------------------------- |
| Events           | Event records with details like name, dates, status, and type |
| Contacts         | Individual people with contact info and profile data          |
| Teams            | Organizational team records                                   |
| Companies        | Company records with organizational details                   |
| Company contacts | Junction data linking contacts to companies                   |
| Event contacts   | Junction data linking contacts to specific events             |
| Event fields     | Custom field schema for the Events entity                     |
| Contact fields   | Custom field schema for the Contacts entity                   |
| Company fields   | Custom field schema for the Companies entity                  |

## Metrics and dimensions

#### Events

| Field       | Type      | Description                                     |
| ----------- | --------- | ----------------------------------------------- |
| id          | Dimension | Unique event identifier                         |
| name        | Dimension | Event name                                      |
| status      | Dimension | Current event status (e.g., planned, completed) |
| start\_date | Dimension | Event start date                                |
| end\_date   | Dimension | Event end date                                  |
| type        | Dimension | Category or type of event                       |
| created\_at | Dimension | When the event record was created               |
| updated\_at | Dimension | When the event record was last updated          |

#### Contacts

| Field       | Type      | Description                              |
| ----------- | --------- | ---------------------------------------- |
| id          | Dimension | Unique contact identifier                |
| first\_name | Dimension | Contact's first name                     |
| last\_name  | Dimension | Contact's last name                      |
| email       | Dimension | Contact's email address                  |
| phone       | Dimension | Contact's phone number                   |
| created\_at | Dimension | When the contact was created             |
| updated\_at | Dimension | When the contact record was last updated |

#### Companies

| Field       | Type      | Description                              |
| ----------- | --------- | ---------------------------------------- |
| id          | Dimension | Unique company identifier                |
| name        | Dimension | Company name                             |
| created\_at | Dimension | When the company record was created      |
| updated\_at | Dimension | When the company record was last updated |

#### Teams

| Field       | Type      | Description               |
| ----------- | --------- | ------------------------- |
| id          | Dimension | Unique team identifier    |
| name        | Dimension | Team name                 |
| created\_at | Dimension | When the team was created |

#### Relationship entities (Company contacts, Event contacts)

| Field                   | Type      | Description                       |
| ----------------------- | --------- | --------------------------------- |
| id                      | Dimension | Relationship record ID            |
| contact\_id             | Dimension | ID of the linked contact          |
| company\_id / event\_id | Dimension | ID of the linked company or event |
| created\_at             | Dimension | When the relationship was created |

#### Custom field definitions (Event fields, Contact fields, Company fields)

| Field       | Type      | Description                   |
| ----------- | --------- | ----------------------------- |
| id          | Dimension | Field identifier              |
| name        | Dimension | Field name/label              |
| field\_type | Dimension | Data type of the custom field |
| required    | Dimension | Whether the field is required |

## Common metric combinations

* **Events + Event contacts + Contacts** — Join all three to see a full attendee list per event with contact details
* **Companies + Company contacts + Contacts** — Build a company-level contact directory with relationship context
* **Events + Event fields** — Understand which custom data points are being tracked across events
* **Contacts + Contact fields** — Audit your contact data model and field usage

## Use cases by role

{% tabs %}
{% tab title="Event managers" %}

* Pull Events and Event contacts to track attendance and participation across all events
* Join Events with Contacts to build per-event attendee reports in Google Sheets or Looker Studio
* Use the Aggregate transformation to count contacts per event and identify your highest-attended events
  {% endtab %}

{% tab title="CRM / Sales ops" %}

* Export Contacts and Company contacts to analyze your contact database and company relationships
* Join Companies with Company contacts and Contacts to build a full account-level view
* Send data to BigQuery for longer-term CRM trend analysis across quarters
  {% endtab %}

{% tab title="Operations" %}

* Use Teams data to understand organizational structure and align event ownership
* Pull custom field definitions (Event fields, Contact fields, Company fields) to audit your data model before migrations or audits
* Append data from multiple Circa accounts into a single destination using Coupler.io's Append transformation
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Custom fields defined in Circa appear in the Event fields, Contact fields, and Company fields entities — the actual values for those fields will appear in the Events, Contacts, and Companies entities respectively
* The **start\_date** parameter controls how far back historical data is pulled — set this carefully to avoid pulling more data than needed
* Relationship entities (Event contacts, Company contacts) only contain IDs — you'll need to join them with the Contacts, Events, or Companies entities to get human-readable data
* Circa is built for event-centric CRM workflows, so Events is typically the anchor entity for most reporting use cases

## Circa common issues

### Connection issues

<details>

<summary>My API key isn't being accepted</summary>

Double-check that you've copied the full API key from your Circa account settings without any leading or trailing spaces. If the key still isn't accepted, try regenerating a new API key in Circa and entering that one instead.

{% hint style="warning" %}
Make sure you're using a Circa API key and not a token from a connected third-party integration — these are different credentials.
{% endhint %}

</details>

<details>

<summary>The data flow fails immediately after I add the source</summary>

This usually means the API key doesn't have sufficient permissions or has been revoked. Check your Circa account to confirm the key is still active. If you're on a restricted Circa plan, some entities may not be accessible via the API.

</details>

### Missing data

<details>

<summary>My events aren't showing up in the output</summary>

Check the start date you set when configuring the source. If the start date is too recent, older events will be excluded. Use the date picker to move the start date further back to capture the full range of events you need.

</details>

<details>

<summary>Custom field values aren't appearing in my data</summary>

Custom field definitions live in the Event fields, Contact fields, and Company fields entities — but the actual values are stored within the Events, Contacts, and Companies entities. Make sure you're pulling the right entity for the values you need, not just the field definitions.

</details>

<details>

<summary>Event contacts or Company contacts show only IDs, no names</summary>

This is expected behavior. The relationship entities only store IDs. You need to use Coupler.io's **Join** transformation to combine Event contacts with the Contacts entity (matching on contact\_id) to enrich the output with contact details.

</details>

### Permission errors

<details>

<summary>I get a 403 or "unauthorized" error when syncing</summary>

This usually means the API key you're using doesn't have access to the entity you've selected. Some Circa plans restrict API access to certain data types. Check your Circa plan and confirm API access is enabled for your account.

</details>

### Data discrepancies

<details>

<summary>The contact count in Coupler.io doesn't match what I see in Circa</summary>

This can happen if the start date filter is excluding older records. Try setting the start date further back to pull a fuller dataset. Also check whether any contacts in Circa were deleted — deleted records are typically not returned by the API.

</details>

### Rate limits

<details>

<summary>My data flow is failing or running slowly due to rate limits</summary>

Circa's API has rate limits that may slow down or interrupt syncs for large datasets. If you hit rate limits, try reducing the number of entities in a single data flow or scheduling syncs during off-peak hours. Splitting large entity pulls across separate data flows can also help.

</details>

## Circa FAQ

<details>

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

Log in to your Circa account and navigate to your account settings or developer settings. Your API key should be listed there. If you don't see it, check with your Circa account administrator — access to the API may depend on your plan or role.

</details>

<details>

<summary>Can I pull data from multiple Circa accounts into one destination?</summary>

Yes. You can add multiple Circa sources to a single data flow — one per account — and use Coupler.io's **Append** transformation to combine the data into one output table. This is useful if your organization manages events across separate Circa workspaces.

</details>

<details>

<summary>Which entities should I use to build an attendee report?</summary>

Start with the **Events** entity to get event details, then add **Event contacts** to get the event-to-contact relationships, and finally add **Contacts** for the actual contact information. Use Coupler.io's **Join** transformation to link these entities on their shared IDs.

</details>

<details>

<summary>What does the start date parameter do?</summary>

The start date controls how far back in time Coupler.io pulls records from Circa. Records created or updated before the start date won't be included in your data flow output. Use the date picker in the source settings to adjust this range.

</details>

<details>

<summary>Can I use Circa data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can send your Circa event or contact data directly to these tools for analysis, summarization, or generating insights from your event CRM data.

</details>

<details>

<summary>Why do my Company contacts and Event contacts only show numbers, not names?</summary>

These are relationship entities — they store IDs that link records together, not the actual contact details. To get readable output, use the **Join** transformation to connect these entities with the Contacts table on the contact\_id field. See the Data Overview for recommended entity combinations.

</details>

<details>

<summary>How often can I refresh Circa data?</summary>

This depends on Circa's API rate limits and your Coupler.io plan. For most use cases, hourly or daily refreshes work well. If you're pulling many entities at once and hitting rate limits, try splitting them across separate data flows or reducing refresh frequency.

</details>

{% hint style="info" %}
For details on available fields and recommended entity combinations, see [Data Overview](#circa-data-overview). For sync errors and permission problems, check [Common Issues](#circa-common-issues). For setup tips specific to Circa, visit [Best Practices](https://docs.coupler.io/sources/category/crm/circa/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/circa.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.
