> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Opa! Suite as a data source

> Bring your Opa! Suite tickets, messages, contacts, customers and service settings to Nekt.

Opa! Suite, by IXC Soft, is an omnichannel customer service platform: WhatsApp, Instagram, Facebook, Telegram, webchat and telephony in one queue of tickets (atendimentos), with attendants, virtual agents (bots), departments and satisfaction surveys. This connector reads your installation's data through the Opa! Suite API and brings every ticket with its full history, the messages of each ticket, customers, contacts, users, departments, ticket reasons, tags, communication channels, message templates and service periods.

> [!NOTE]
>
> The connector only reads data. It never creates, changes or deletes anything in Opa! Suite.

## Before you start

The connector uses the API token of an Opa! Suite user. You need the **Grupos de permissão** and **Alterar permissões dos usuários** permissions in Opa! Suite to set it up. We recommend a user only for this integration.

1. **Create an API permission group.** In Opa! Suite, go to **Configurações → Permissões** and click **Adicionar novo**. Give it a name, turn on **Grupo exclusivo para API** and save. Open the group, go to the **Permissões** tab and mark **Visualizar** for the data you want to sync (see the table below). In a new API group every permission starts unmarked.
2. **Give the user API access.** Go to **Usuários**, open the integration user and, in **Cadastro → Permissões**, click **Editar informações**. Turn on **Possui acesso à API do sistema**, choose the group you created in **Grupo de permissões da API** and save.
3. **Copy the token.** The window **Token API gerado com sucesso** shows the token **only once**. Copy it before closing the window. If you lose it, click **Gerar novo token** in the same place (the previous token stops working at once).
4. **Find your Opa! Suite Address.** It is the address you open in the browser, with `https` and nothing after the domain, for example `https://yourcompany.opasuite.com.br`.

| Table | Permission in the API group (Visualizar) |
| :- | :- |
| Tickets, Messages | Atendimentos → Atendimentos |
| Customers | Contatos → Clientes e fornecedores |
| Contacts | Contatos → Todos os contatos |
| Users | Configurações → Usuários |
| Departments | Configurações → Departamentos |
| Ticket reasons | Configurações → Motivos de atendimento |
| Tags | Configurações → Etiquetas |
| Communication channels | Configurações → Canais de comunicação |
| Message templates | Configurações → Modelos de mensagem |
| Service periods | Configurações → Períodos de atendimento |

> [!WARNING]
>
> If the API permission group restricts the allowed networks (**Configurações → Permissões → the group → Preferências do grupo → Redes permitidas**), add Nekt's IP addresses to that list: `34.24.209.97`, `34.74.81.117` and `34.138.230.39`. These are the addresses of Nekt Express. If your Nekt workspace runs on your own cloud account (GCP or AWS), ask Nekt support for the addresses to allow. If your Opa! Suite runs on your own server, its firewall must also accept connections from these addresses.

## Configuring Opa! Suite as a Source

In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the Opa! Suite option from the list of connectors.

Click **Next** and you'll be prompted to add your access.

### 1. Add account access

The following configurations are available:

* **Opa! Suite Address**: the address of your installation, with `https` and nothing after the domain, for example `https://yourcompany.opasuite.com.br`. The address must be reachable from the internet.
* **API Token**: the token of the integration user (see [Before you start](#before-you-start)).
* **Start Date**: the earliest ticket opening or closing date synced, for Tickets and Messages. The other tables are always read in full.

> [!NOTE]
>
> One source reads one Opa! Suite installation. If you have more than one, create one source for each, with its own address and token.

Once you're done, click **Next**.

### 2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.

> Tip: The stream can be found more easily by typing its name.

Select only the tables your API permission group can read. A table without permission is skipped in every sync and shown as failed.

Select the streams and click **Next**.

### 3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.

* **Layer**: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
* **Folder**: a folder can be created inside the selected layer to group all tables being created from this new data source.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** to all tables at once and make this process faster!
* **Sync Type**: keep the suggested type. Tickets and Messages are **Incremental**: each sync reads only the tickets opened or closed in the last days and merges them into the table. The other tables are **Full table**: Opa! Suite gives no change date for them, so each sync reads them whole and replaces the table.

> [!WARNING]
>
> Keep **Messages** as Incremental. As Full table, every sync would read the messages of every ticket since the Start Date again.

Once you are done configuring, click **Next**.

### 4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters.

To define your [Trigger](https://docs.nekt.com/runs/scheduling-and-triggers.md), consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). We recommend a **daily** sync. Each sync reads again the last 3 to 4 days of tickets, every ticket still open and their messages, all from your Opa! Suite server, so syncing more often than that adds load to your server without bringing much new data.

Optionally, you can configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource [here](https://docs.nekt.com/get-started/core-concepts/resource-control).

Once you are ready, click **Next** to finalize the setup.

### 5. Check your new source

You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

> [!WARNING]
>
> For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.

# Streams and Fields

## Available streams

The table below lists every stream, its **slug** (the exact identifier to pass when creating the source via API) and a short description.

| Stream | Slug | Sync | Description |
| - | - | - | - |
| Tickets | `atendimentos` | Incremental | Every ticket (atendimento) opened or closed since the Start Date, with status, channel, attendants, transfers, ratings and notes. |
| Messages | `mensagens` | Incremental | The messages of each ticket: who sent them, content, type and delivery status. |
| Customers | `clientes` | Full table | Customers and suppliers registered in Opa! Suite. |
| Contacts | `contatos` | Full table | Contacts (people who talk to you) with their phone numbers and linked customer. |
| Users | `usuarios` | Full table | Attendants and virtual agents (bots). |
| Departments | `departamentos` | Full table | Departments and their service settings. |
| Ticket reasons | `motivos` | Full table | Reasons that can be set on tickets. |
| Tags | `etiquetas` | Full table | Tags that can be set on tickets. |
| Communication channels | `canais_comunicacao` | Full table | WhatsApp, Instagram, webchat and other channels connected to Opa! Suite. |
| Message templates | `templates` | Full table | Message templates (for example, WhatsApp templates). |
| Service periods | `periodos_atendimento` | Full table | Business hours used by the departments. |

Join `atendimentos.setor` with `departamentos.id`, `atendimentos.id_atendente` with `usuarios.id`, `atendimentos.id_user` with `contatos.id`, `atendimentos.id_cliente` with `clientes.id`, `atendimentos.canal_id` with `canais_comunicacao.id` and `mensagens.id_rota` with `atendimentos.id`.

## Fields by stream

Fields marked String (JSON) hold a nested object or list as JSON text; use your warehouse's JSON functions to read them. Dates and times are in UTC. Every table also has an `other_fields` column (String, JSON) with any field Opa! Suite returned that has no column of its own; it is empty when every field is mapped.

> [accordion] Tickets
>
> Every ticket (atendimento) opened or closed since the Start Date.
>
> Table: `atendimentos` · Primary key: `id` · Sync: Incremental (`last_activity_at`)
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the ticket. |
> | `protocolo` | String | Protocol number shown to the customer. |
> | `status` | String | `AG` (waiting), `EA` (in service), `PS` (in satisfaction survey) or `F` (finished). |
> | `canal` | String | Kind of channel the ticket came through (for example `whatsapp`, `page`). |
> | `canal_id` | String | Communication channel (`canais_comunicacao.id`). |
> | `canal_cliente` | String | Identifier of the customer in the channel (for example the phone number). |
> | `id_cliente` | String | Customer (`clientes.id`), when linked. |
> | `id_user` | String | Contact who talks in the ticket (`contatos.id`). |
> | `id_atendente` | String | Attendant or virtual agent currently or last responsible (`usuarios.id`). |
> | `setor` | String | Department (`departamentos.id`). |
> | `descricao` | String | Description of the ticket. |
> | `aberto_por` | String | Who opened the ticket: the contact or an attendant. |
> | `finalizado_por` | String | Who finished the ticket, when finished. |
> | `date` | Datetime | When the ticket was opened. |
> | `inicio` | Datetime | When the ticket was taken by an attendant or left the virtual agent. |
> | `update` | Datetime | Last interaction, when informed. |
> | `fim` | Datetime | When the ticket was finished. |
> | `id_motivo_atendimento` | String | Reason of the ticket (`motivos.id`), when set. |
> | `motivos` | String (JSON) | Reasons set on the ticket. |
> | `tags` | String (JSON) | Tags set on the ticket (`etiquetas.id`). |
> | `avaliacoes` | String (JSON) | Satisfaction ratings given by the customer. |
> | `evaluations` | String (JSON) | Ratings of the ticket, including AI and Likert ratings. |
> | `observacoes` | String (JSON) | Notes added to the ticket. |
> | `atendentes` | String (JSON) | Attendants who worked on the ticket, with department, start, end and whether it was human. |
> | `operacoes` | String (JSON) | Operations on the ticket (opening, transfers, finishing) with department, attendant and date. |
> | `usuarios_acompanhar` | String (JSON) | Users following the ticket. |
> | `transferencias_call_center` | String (JSON) | Transfers to the call center. |
> | `solicitacoes` | String (JSON) | Requests registered in the ticket. |
> | `inatividade` | String (JSON) | Inactivity action applied to the ticket and when. |
> | `aguardando_cliente` | Boolean | Whether the ticket is waiting for the customer's answer. |
> | `nivel_prioridade_listagem` | Integer | Priority used to order the ticket in the lists. |
> | `tipo_usuario_responsavel` | String | Kind of user responsible for the ticket, when informed. |
> | `language` | String | Language of the ticket. |
> | `country` | String | Country of the ticket. |
> | `created_at` | Datetime | When the ticket record was created. |
> | `updated_at` | Datetime | When the ticket record was last changed, when informed. |
> | `last_activity_at` | Datetime | Latest of the opening, start, last interaction, finish and update times, computed by Nekt. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Messages
>
> The messages of each ticket.
>
> Table: `mensagens` · Primary key: `id` · Sync: Incremental (`atendimento_last_activity_at`)
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the message. |
> | `id_rota` | String | Ticket the message belongs to (`atendimentos.id`). |
> | `id_atend` | String | Attendant or virtual agent who sent the message (`usuarios.id`), when sent from Opa! Suite. |
> | `id_user` | String | Contact who sent the message (`contatos.id`), when sent by the customer. |
> | `mensagem` | String | Content of the message: the text, or a JSON object for structured messages (for example interactive menus). |
> | `tipo` | String | Type of message (for example `texto`, `menuInterativo`). |
> | `objeto` | String (JSON) | Attached file, media or location, when any. |
> | `chamada` | String (JSON) | Call data, for messages that record a call. |
> | `canal_comunicacao` | String | Communication channel (`canais_comunicacao.id`). |
> | `destinatario` | String | Recipient (a contact or a user, see `tipo_destinatario`). |
> | `tipo_destinatario` | String | `clientes_users` (a contact) or `usuarios` (a user). |
> | `id_mensagem_citada` | String | Message quoted (replied to), when any. |
> | `id_mensagem_canal` | String | Identifier of the message at the channel provider. |
> | `status_envio` | String (JSON) | Delivery status at the channel. |
> | `data` | Datetime | When the message was sent. |
> | `created_at` | Datetime | When the message record was created. |
> | `updated_at` | Datetime | When the message record was last changed. |
> | `atendimento_last_activity_at` | Datetime | Last activity of the message's ticket when it was read. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Customers
>
> Table: `clientes` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the customer in Opa! Suite. |
> | `id_externo` | String | Identifier of the customer in the integrated management system (ERP), when it came from it. |
> | `nome` | String | Company or person name. |
> | `fantasia` | String | Trade name. |
> | `cpf_cnpj` | String | CPF or CNPJ. |
> | `status` | String | `A` (active) or `I` (inactive). |
> | `prospect` | Boolean | Whether the record is a prospect. |
> | `cliente` | Boolean | Whether the record is a customer. |
> | `fornecedor` | Boolean | Whether the record is a supplier. |
> | `prestador_servico` | Boolean | Whether the record is a service provider. |
> | `id_fornecedor` | String | Identifier of the supplier in the management system, when informed. |
> | `id_filial` | String | Branch the customer belongs to, when informed. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Contacts
>
> Table: `contatos` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the contact. |
> | `nome` | String | Name of the contact. |
> | `email_principal` | String | Main email address. |
> | `cli_emp` | String | Customer the contact is linked to (`clientes.id`). |
> | `fones` | String (JSON) | Phone numbers, with type and whether they are WhatsApp or mobile. |
> | `lead` | Boolean | Whether the contact is a lead. |
> | `classificacao` | String | Classification of the contact. |
> | `historico_email` | Boolean | Whether the email history is kept. |
> | `habilitar_alerta` | Boolean | Whether alerts are enabled. |
> | `requer_autenticacao_sempre` | Boolean | Whether the contact must always authenticate. |
> | `opt_in_opt_out` | String (JSON) | Opt-in and opt-out history for communications. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Users
>
> Table: `usuarios` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the user or virtual agent. |
> | `nome` | String | Name. |
> | `status` | String | `A` (active) or `I` (inactive). |
> | `tipo` | String | `user` (a person) or `bot` (virtual agent). |
> | `email` | String | Email address, when informed. |
> | `departamento` | String | Main department (`departamentos.id`), when informed. |
> | `empresa` | String | Company the user belongs to, when informed. |
> | `online` | String | Presence when the data was read. |
> | `genero` | String | Gender, when informed. |
> | `pais` | String | Country, when informed. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. Tokens and passwords are never stored. |

> [accordion] Departments
>
> Table: `departamentos` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the department. |
> | `nome` | String | Name. |
> | `descricao` | String | Description. |
> | `status` | String | `A` (active) or `I` (inactive). |
> | `ordem` | Integer | Display order. |
> | `notifica_ag` | String | Setting for notifying waiting tickets. |
> | `motivo_atendimento` | Boolean | Whether a reason must be set on the tickets. |
> | `realiza_atendimento` | Boolean | Whether the department handles tickets. |
> | `observacao_atendimento` | Boolean | Whether a note must be set on the tickets. |
> | `flow_avaliacao` | String | Flow used for the satisfaction survey, when set. |
> | `encerramento_inatividade_avaliacao` | Integer | Inactivity time that closes the satisfaction survey. |
> | `cod_pabx` | Integer | Code in the phone system (PABX). |
> | `tipo_encaminhamento_ligacoes` | String | How calls are forwarded to the department. |
> | `encaminhar_ligacao_todos_atendentes` | Boolean | Whether calls ring for every attendant. |
> | `encerrar_atend_pabx_ao_desligar` | Boolean | Whether a phone ticket is closed when the call hangs up. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Ticket reasons
>
> Table: `motivos` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the reason. |
> | `motivo` | String | Name of the reason. |
> | `departamentos` | String (JSON) | Departments where the reason can be used. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Tags
>
> Table: `etiquetas` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the tag. |
> | `nome` | String | Name of the tag. |
> | `cor` | String | Color of the tag. |
> | `id_criador` | String | User who created the tag (`usuarios.id`), when informed. |
> | `empresa` | String | Company the tag belongs to, when informed. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Communication channels
>
> Table: `canais_comunicacao` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the channel. |
> | `nome` | String | Name of the channel. |
> | `canal` | String | Kind of channel (Whatsapp, Instagram, Page, Telegram, Messenger, Telefonia). |
> | `integracao` | String | Integration that connects the channel (for example `facebook`, `dialog360`). |
> | `status` | String | `A` (active) or `I` (inactive). |
> | `id_atendente` | String | Virtual agent or user that answers the channel first (`usuarios.id`). |
> | `prioridade_listagem_atendimentos` | Integer | Priority of the channel's tickets in the lists. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Message templates
>
> Table: `templates` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the template. |
> | `atalho` | String | Shortcut (name) of the template. |
> | `texto` | String | Text of the template, with its `{{variables}}`. |
> | `tipo_mensagem` | String | Integration the template belongs to (for example `dialog360`). |
> | `departamentos` | String (JSON) | Departments that can use the template. |
> | `dados` | String (JSON) | Settings of the template at the provider (category, language, buttons). |
> | `identificador_canal` | String | Identifier of the template at the channel provider. |
> | `anexo` | String (JSON) | Attachment of the template, when any. |
> | `flow` | String | Flow started by the template, when any. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

> [accordion] Service periods
>
> Table: `periodos_atendimento` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the service period. |
> | `nome` | String | Name of the service period. |
> | `ativo` | Boolean | Whether it is active. |
> | `periodos` | String (JSON) | Time ranges: weekdays, holidays, start and end times. |
> | `created_at` | Datetime | When the record was created, when informed. |
> | `updated_at` | Datetime | When the record was last changed, when informed. |
> | `other_fields` | String (JSON) | Fields with no column of their own. |

## Implementation Notes

### Data Quality Considerations

* **Tickets are read by opening and by closing date.** Each sync reads the tickets opened or closed since the last sync (minus 2 days, to catch late updates). A ticket opened long ago comes back with its final state when it is closed.
* **Open tickets** (waiting, in service or in satisfaction survey) are read again on every sync until they close, whatever their age (Opa! Suite lists open tickets of the last 365 days). All their messages are read again on every sync too, so new messages of an open ticket arrive with the next sync.
* **A change to a ticket that is already closed** (for example, a rating given days later) is only picked up if it happens within 2 days of the ticket's last activity read. A full sync brings every ticket up to date.
* **Tickets opened before the Start Date** but closed after it are included.
* **Permissions**: each table needs its permission in the API group (see [Before you start](#before-you-start)). If the group cannot read a table, that table is skipped and not updated, the other tables keep syncing, and the sync log names the table and the permission to give.
* **Full table tables are never half updated.** The connector reads all the data of a full table table before writing any of it. If Opa! Suite fails while it is read, nothing of that table is sent and the sync shows it as failed.
* **Tokens and passwords** that the API may return for users are never stored.

### API Limits & Performance

* Opa! Suite does not publish a request limit, and the API runs on your installation's server. The connector sends one request at a time, with a short pause between them, and waits when the server asks it to slow down.
* **Messages are read one ticket at a time**: the first sync makes one request per ticket since the Start Date. Choose a Start Date that keeps the first sync manageable (for example, the last few months), and let later syncs keep the table up to date.
* Tickets are read one week at a time. If Opa! Suite does not apply the date or status filters as documented, the Tickets or Messages table fails with a message, instead of loading an incomplete history.

## Troubleshooting

| Error or symptom | What it means | What to do |
| :- | :- | :- |
| "Opa! Suite rejected the API token of this source" | The token is wrong, was replaced by a new one, or the user lost API access. | In Opa! Suite, open **Usuários → the user → Cadastro → Permissões**, check that **Possui acesso à API do sistema** is on, generate a new token if needed and update the source. |
| "Opa! Suite refused the connection from Nekt because the network is not allowed" | The API group restricts the allowed networks and Nekt's addresses are not in the list. | Add Nekt's IP addresses to **Redes permitidas** of the API group (see [Before you start](#before-you-start)), or leave the list empty. |
| "Some selected tables cannot be read with this source's token" | The API group does not have the permission of those tables. They were skipped; the other tables loaded. | Mark the permission named in the message in **Configurações → Permissões → the API group → Permissões**, or deselect those tables. |
| "None of the selected tables can be read with this source's token" | The API group cannot read any selected table. | Mark the permissions of the tables you want in the API group. |
| "This Opa! Suite installation does not offer ... in its API" | The installation has no API route for that table, usually because it runs an older version. | Update Opa! Suite or deselect the table. |
| "The Opa! Suite Address of this source is not valid" | The address has `http`, a path (such as `/atendente`), user, password or parameters, or it is an IP address or a local name. | Use only `https://` plus the domain, for example `https://yourcompany.opasuite.com.br`. |
| "...was not found on the internet" or "...points to a private network" | The address does not exist, or it is a local network address Nekt cannot reach. | Check the address for typos. The server must be reachable from the internet. |
| "Could not connect to the Opa! Suite server at ..." | Nekt could not reach the server. | Check that the server is on and that its firewall accepts connections from Nekt's IP addresses. |
| "...presented a security certificate that is not trusted" | The `https` certificate of the server is expired, self-signed or issued for another name. | Check that the address is exactly your installation's, and ask the server's administrator to install a valid certificate. |
| "...did not answer like the Opa! Suite API" or "...redirected the request" | The address opens a web page instead of the API. | Use the address of your installation, with nothing after the domain. |
| "Opa! Suite refused the request Nekt made to read ... (Opa! Suite said: '...')" | Opa! Suite rejected the request for that table. | Contact Nekt support with the message. |
| "The Opa! Suite server asked Nekt to slow down" | The server limited how fast the sync may read. | No action needed; the sync waits and continues. |
| "The Opa! Suite server kept failing" or "...is answering with errors right now" | The server did not answer, or answered with errors, after several attempts. | Usually temporary; the next sync tries again. If it repeats, contact Nekt support. |
| "The Opa! Suite API answered in an unexpected way" | The API changed or answered in an unexpected way. | Contact Nekt support. |

## Skills for agents

<Snippet file="agent-skills-intro.mdx" />

> [card] [Download Opa! Suite skills file](https://docs.nekt.com/sources/opa-suite.md)
>
> Opa! Suite connector documentation as plain markdown, for use in AI agent contexts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.