> ## 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.

# Fortics Chat Center as a data source

> Bring attendances, messages, contacts, agents, teams, channels, tabulations and tags from Fortics Chat Center to Nekt.

Fortics Chat Center (formerly SZ.chat) is Fortics' omnichannel customer service platform: WhatsApp, web chat, Instagram, Telegram and other channels in one place, with chatbot flows, teams of agents and attendance reports. This connector brings the finished attendances with their messages, the monthly attendance report, the contacts and the registers you need to read them: agents, administrators, teams, channels, tabulations, tags, user groups, pauses, time groups, contact groups and predefined messages.

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

## Configuring Fortics Chat Center 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 Fortics Chat Center option from the list of connectors.

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

### 1. Add account access

The connector signs in to your Fortics Chat Center instance with the **e-mail and password of a user**, the same ones used to sign in to the web app. Use an **administrator** (Settings > Administrators) that signs in with a password, not through single sign-on. We recommend a user created for Nekt, so that a password change by a person does not stop your syncs.

The following configurations are available:

* **Fortics Chat Center URL**: The address you open Fortics Chat Center with, for example `https://yourcompany.sz.chat`. Only the address of your instance is used, and it must start with `https://`.
* **E-mail**: Login e-mail of the user.
* **Password**: Password of that user.
* **Start Date**: Earliest date of the attendances, messages and monthly reports read on the first sync. Registers (contacts, agents, teams and the others) are always read in full.
* **Attendance Lookback (days)** (advanced, default 3): Days before the last sync that are read again on every sync, so attendances that finish or change late are updated. Use 1 to 31.

> [!WARNING]
>
> An agent user (instead of an administrator) can be refused some tables, such as the monthly attendance report, and may not be able to sign in outside its working hours. Tables the user cannot read are skipped with a warning naming them; the others still load.

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 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**: you can choose between INCREMENTAL and FULL\_TABLE.
  * Incremental: every time the extraction happens, we'll get only the new data. Attendances, their messages and the monthly report are incremental.
  * Full table: every time the extraction happens, we'll get the current state of the data. Contacts and the registers are always read in full.

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).

Optionally, you can define some additional settings:

* 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).
* Determine when to execute an **Additional [Full Sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#additional-full-sync)**. Fortics Chat Center keeps attendance history only for the storage period of your plan, so a full sync of **Attendances** or **Attendance Messages** reloads only what Fortics still keeps; older rows leave the table. Prefer the incremental sync for these tables.

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 | Description |
| - | - | - |
| Attendances | `attendances` | Finished attendances with team, agent, contact, channel, tabulation, tags and timers. |
| Attendance Messages | `attendance_messages` | Messages of each finished attendance. |
| Attendance Report (Monthly) | `attendance_report_monthly` | Attendances, messages and HSM messages per month, channel, team and agent. |
| Contacts | `contacts` | Contacts and their identifiers on each platform. |
| Contact Groups | `contact_groups` | Contact groups. |
| Agents | `agents` | Agents, their teams and working hours. |
| Administrators | `admins` | Administrators of the instance. |
| Teams | `teams` | Teams ("Equipes") and their settings. |
| User Groups | `user_groups` | User groups (permission profiles). |
| Pauses | `pauses` | Pause types. |
| Time Groups | `time_groups` | Business-hours groups. |
| Channels | `channels` | Service channels (WhatsApp, web chat, Telegram, Instagram...). |
| Tabulations | `tabulations` | Classifications given when an attendance ends. |
| Tags | `tags` | Tags agents put on attendances. |
| Predefined Messages | `predefined_messages` | Predefined (quick reply) messages. |

## Fields by stream

Every table also has an `extra_fields` column (JSON) with any other field Fortics Chat Center returned for the record. Credentials (tokens, passwords, keys) are never loaded.

### Attendances

> [accordion] Attendances
>
> Finished attendances (conversations handled by the bot or by an agent), one row per attendance, with the team, agent, channel, contact, tabulation, tags, events and the waiting and handling times. Attendances in progress appear after they finish.
>
> Table: `attendances` · Primary key: `id` · Sync: Incremental
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the attendance record in the Fortics history. |
> | `detail_id` | String | Identifier of the attendance in the detail answer, when it differs from id. |
> | `session_id` | String | Identifier of the session (conversation) the attendance belongs to. |
> | `protocol` | String | Attendance protocol number shown to the contact. |
> | `status_attendance` | String | Outcome of the attendance as Fortics classifies it: success or loss. |
> | `status` | String | Last status of the session (auto, wait, attendance). |
> | `contact_id` | String | Identifier of the contact; see the contacts table. |
> | `contact_name` | String | Name of the contact. |
> | `contact_number` | String | Phone number of the contact. |
> | `email` | String | E-mail of the contact, when the list returns it. |
> | `platform` | String | Platform of the attendance (Whatsapp, WhatsappBusiness, ChatWeb, Telegram, Instagram...). |
> | `platform_id` | String | Identifier of the contact on that platform (phone number, user id...). |
> | `channel_id` | String | Identifier of the channel; see the channels table. |
> | `channel_description` | String | Name of the channel. |
> | `campaign_id` | String | Identifier of the team (campaign) that handled the attendance; see the teams table. |
> | `campaign_name` | String | Name of the team that handled the attendance. |
> | `agent_id` | String | Identifier of the agent that handled the attendance; see the agents table. |
> | `agent_name` | String | Name of the agent that handled the attendance. |
> | `group` | String | Routing group of the session. |
> | `created_at` | String | When the attendance started, as returned by Fortics. |
> | `finished_at` | String | When the attendance finished, as returned by Fortics (local time of the instance; see the timezone column). |
> | `updated_at` | String | When the attendance record was last changed, as returned by Fortics. |
> | `report_at` | String | When the attendance was consolidated for reports, as returned by Fortics. |
> | `timer_on_wait` | String | When the contact entered the waiting queue (local time of the instance). |
> | `timer_accept` | String | When an agent accepted the attendance (local time of the instance). |
> | `last_interaction` | String | Last interaction in the session, as returned by Fortics. |
> | `last_message` | String | Text of the last message of the session. |
> | `last_message_date_contact` | String | When the contact sent the last message (local time of the instance). |
> | `wait` | String | Waiting time of the session as shown by Fortics (HH:MM:SS). |
> | `total_time_seconds` | Integer | Total attendance time in seconds (TTA in Fortics). |
> | `handling_time_seconds` | Integer | Time with an agent, in seconds (TMA in Fortics). |
> | `waiting_time_seconds` | Integer | Time waiting for an agent, in seconds (TME in Fortics). |
> | `timezone` | String | Time zone Fortics uses for the local times of this attendance (e.g. America/Fortaleza). |
> | `tabulation` | String | Tabulation (classification) given when the attendance ended (JSON). |
> | `tags` | String | Tags and flow answers recorded in the session (JSON array). |
> | `events` | String | Events of the session, such as flow start, wait and transfers, with their times (JSON array). |
> | `agents_conference` | String | Agents invited to a conference in the session (JSON array). |
> | `is_attendance` | Boolean | Whether the session reached human attendance. |
> | `finish_session` | Boolean | Whether the session was closed. |
> | `message_count` | Integer | Number of messages of the attendance (rows in attendance\_messages). |
> | `detail_available` | Boolean | Whether Fortics still returned the full detail of the attendance; false means only the list fields are filled. |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Attendance Messages
>
> Every message of each finished attendance: who sent it (contact, agent or bot), its type and text, and when it was sent.
>
> Table: `attendance_messages` · Primary key: `attendance_id`, `message_id` · Sync: Incremental
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `attendance_id` | String | Identifier of the attendance the message belongs to; see the attendances table. |
> | `message_id` | String | Unique identifier of the message (or position-N when Fortics gives none). |
> | `position` | Integer | Position of the message in the conversation, starting at 0. |
> | `session_id` | String | Identifier of the session (conversation). |
> | `protocol` | String | Protocol number of the attendance. |
> | `origin` | String | Who sent the message: channel (the contact), agent, auto (bot/flow)... |
> | `type` | String | Message type (text, image, audio, document...). |
> | `message` | String | Text of the message. |
> | `filename` | String | File name, for media messages. |
> | `created_at` | String | When the message was sent (local time of the instance). |
> | `blocked` | Boolean | Whether the message was blocked. |
> | `privacy` | String | Privacy setting of the message. |
> | `request_id` | String | Request identifier of the message, when sent through the API. |
> | `message_ref` | String | Identifier of the message in the channel provider. |
> | `wbs_session_category` | String | WhatsApp Business conversation category of the message. |
> | `wbs_session_billable` | Boolean | Whether the WhatsApp Business conversation is billable. |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Attendance Report (Monthly)
>
> Fortics' attendance report ("Atendimentos Business") per month, channel, team and agent: number of attendances, messages and HSM (WhatsApp template) messages. Requires an administrator user.
>
> Table: `attendance_report_monthly` · Primary key: `month`, `channel_description`, `campaign_name`, `agent_login`, `agent_name` · Sync: Incremental
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `month` | String | Month of the figures (YYYY-MM); the current month holds running totals until it closes. |
> | `channel_description` | String | Channel name with its number, as Fortics shows it (empty when not informed). |
> | `campaign_name` | String | Team name (empty when not informed). |
> | `agent_login` | String | Login e-mail of the agent (empty when not informed). |
> | `agent_name` | String | Name of the agent (empty when not informed). |
> | `attendances` | Integer | Number of attendances. |
> | `total_messages` | Integer | Total number of messages. |
> | `total_session_messages` | Integer | Messages sent inside a conversation session (not HSM templates). |
> | `total_hsm` | Integer | Messages sent as HSM (WhatsApp template) messages. |
> | `extracted_at` | String | When this row was read (UTC, ISO 8601). A re-read month gets new rows; a row whose channel, team or agent was renamed keeps its old name and an older extracted\_at, so keep only the rows with the latest extracted\_at of each month. |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

### Contacts

> [accordion] Contacts
>
> Every contact of your Fortics Chat Center, with their identifiers on each platform and their contact groups.
>
> Table: `contacts` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `name` | String | Contact name. |
> | `email` | String | Contact e-mail. |
> | `number` | String | Main phone number of the contact (with country code). |
> | `final_number` | String | Phone number formatted as area code + number. |
> | `ddi` | String | Country calling code of the contact's phone. |
> | `ddd` | String | Area code of the contact's phone. |
> | `platforms` | String | Identifiers of the contact on each platform: list of `platform` and `platform_id` pairs (JSON array). |
> | `channels` | String | Identifier of the contact on each channel type (JSON object). |
> | `groups` | Array of strings | Identifiers of the contact groups of the contact; see the contact\_groups table. |
> | `last_channel` | String | Identifier of the last channel the contact used; see the channels table. |
> | `last_interaction` | String | Last interaction of the contact, as returned by Fortics. |
> | `status_whatsapp` | Integer | WhatsApp status code of the contact's number. |
> | `opt_in` | String | Opt-in status of the contact. |
> | `optin_gupshup` | Boolean | Whether the contact opted in through Gupshup. |
> | `default_language` | String | Preferred language of the contact. |
> | `observation` | String | Agent annotation saved on the contact. |
> | `photo` | String | File name of the contact's photo. |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Contact Groups
>
> Contact groups used to segment contacts.
>
> Table: `contact_groups` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `name` | String | Contact group name. |
> | `opt_in` | String | Opt-in setting of the group. |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

### Team and operation

> [accordion] Agents
>
> Agents (attendants), their teams, working hours and permissions.
>
> Table: `agents` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `type` | String | User type (agent). |
> | `name` | String | Agent name. |
> | `email` | String | Agent login e-mail. |
> | `codename` | String | Agent codename, used to reach the agent directly (e.g. @maria). |
> | `ramal` | String | Phone extension of the agent. |
> | `begin` | String | Start of the agent's working hours (HH:MM). |
> | `end` | String | End of the agent's working hours (HH:MM). |
> | `history` | String | Which attendance history the agent may see: all, campaign (own teams) or not\_apply. |
> | `language` | String | Interface language of the agent. |
> | `default_language` | String | Default language of the agent. |
> | `status` | String | Last known presence status of the agent (online, offline, paused...). |
> | `campaigns` | Array of strings | Identifiers of the teams (campaigns) the agent belongs to; see the teams table. |
> | `groups` | Array of strings | Identifiers of the contact groups assigned to the agent; see the contact\_groups table. |
> | `enable_login_with_remote_auth` | Boolean | Whether the agent signs in through a remote identity provider (single sign-on). |
> | `agent_permission` | String | Agent permissions, such as simultaneous attendances and their limit (JSON object). |
> | `pause` | String | Pause in progress when the list was read, if any (JSON). |
> | `photo` | String | File name of the agent's photo. |
> | `logged_at` | String | Last time the agent logged in, as returned by Fortics. |
> | `last_login` | String | Last login of the agent, as returned by Fortics. |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Administrators
>
> Administrators of the instance and their permission profile.
>
> Table: `admins` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `type` | String | User type (admin). |
> | `name` | String | Administrator name. |
> | `email` | String | Administrator login e-mail. |
> | `group_id` | String | Identifier of the user group (permission profile) of the administrator; see the user\_groups table. |
> | `enable_login_with_remote_auth` | Boolean | Whether the administrator signs in through a remote identity provider (single sign-on). |
> | `photo` | String | File name of the administrator's photo. |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Teams
>
> Teams ("Equipes"; called campaigns in the Fortics API) with their agents, tabulations, tags and attendance rules.
>
> Table: `teams` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `name` | String | Team name. |
> | `history` | String | Attendance history rule of the team (all, session or campaign). |
> | `rule_attendance` | String | How attendances are distributed among agents (AllAgents, AgentsLess, Sequence, GroupContacts). |
> | `transhipment` | String | Identifier of the overflow team that receives attendances when this team cannot. |
> | `transhipment_name` | String | Name of the overflow team. |
> | `agents` | Array of strings | Identifiers of the agents that may log in to this team; see the agents table. |
> | `tabulations` | Array of strings | Identifiers of the tabulations (closing reasons) available to the team; see the tabulations table. |
> | `tags` | Array of strings | Identifiers of the tags available to the team; see the tags table. |
> | `predefined` | Array of strings | Identifiers of the predefined messages of the team; see the predefined\_messages table. |
> | `can_be_disabled` | Boolean | Whether an agent may disable this team in their session. |
> | `optin_start` | Boolean | Whether the team may only start conversations with opted-in contacts. |
> | `has_online_agents` | Boolean | Whether the team had agents online when the list was read. |
> | `has_offline_attendance` | Boolean | Whether the team offers offline attendance. |
> | `message_end` | String | Message sent to the contact when an attendance of the team ends. |
> | `message_agent` | String | Message sent when no agent of the team is available. |
> | `timer` | String | Session time of the team: days, hours and minutes (JSON object). |
> | `timer_wait` | String | Transfer by waiting time: enabled, limit, unit and destination team (JSON object). |
> | `permissions` | String | Permissions of the team's agents (JSON object). |
> | `sequence` | String | Order of agents for sequential distribution (JSON array). |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] User Groups
>
> User groups (permission profiles).
>
> Table: `user_groups` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `name` | String | User group name. |
> | `master` | Boolean | Whether the group has every permission. |
> | `permissions` | String | Permissions of the group (JSON array). |
> | `view_by_teams` | Boolean | Whether the group is restricted to some teams. |
> | `general_selected_teams` | Array of strings | Identifiers of the teams the group is restricted to. |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Pauses
>
> Pause types agents can take.
>
> Table: `pauses` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `name` | String | Pause name. |
> | `description` | String | Pause description. |
> | `active` | Boolean | Whether the pause is active. |
> | `productive` | Boolean | Whether the pause counts as productive time. |
> | `cumulative` | Boolean | Whether the pause is cumulative. |
> | `supervisioned` | Boolean | Whether the pause is supervised. |
> | `continue_attendance` | Boolean | Whether the agent keeps attending during the pause. |
> | `initial_time` | String | Start time of the pause (HH:MM). |
> | `max_time` | String | Maximum duration of the pause, as configured. |
> | `message` | String | Away message of the pause. |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Time Groups
>
> Business-hours groups used by flows and teams.
>
> Table: `time_groups` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `name` | String | Time group name. |
> | `schedule` | String | Time ranges of the group: days, months, weekdays and hours (JSON array). |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

### Channels and classifications

> [accordion] Channels
>
> Service channels (WhatsApp numbers, web chats, Telegram bots, Instagram and others). Channel credentials are never loaded.
>
> Table: `channels` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `platform` | String | Platform of the channel (Whatsapp, WhatsappBusiness, ChatWeb, Telegram, Messenger, Instagram...). |
> | `provider` | String | Provider behind the channel. |
> | `description` | String | Channel name. |
> | `number` | String | Phone number or account of the channel. |
> | `flow_id` | String | Identifier of the chatbot flow that answers the channel. |
> | `status` | String | Connection status of the channel (connected, qrcode...). |
> | `enabled` | Boolean | Whether the channel is enabled. |
> | `receptive` | Boolean | Whether the channel is receptive. |
> | `whatsapp_broker` | String | WhatsApp Business provider of the channel (e.g. gupshup). |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Tabulations
>
> Tabulations: the classifications (closing reasons) an agent gives when an attendance ends.
>
> Table: `tabulations` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `name` | String | Tabulation name (classification given when an attendance ends). |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Tags
>
> Tags agents put on attendances, and the teams that may use each one.
>
> Table: `tags` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `name` | String | Tag name. |
> | `type` | String | Tag type. |
> | `campaigns` | Array of strings | Identifiers of the teams that may use the tag; see the teams table. |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

> [accordion] Predefined Messages
>
> Predefined (quick reply) messages.
>
> Table: `predefined_messages` · Primary key: `id` · Sync: Full table
>
> | Field | Type | Description |
> | :- | :- | :- |
> | `id` | String | Unique identifier of the record in Fortics Chat Center. |
> | `description` | String | Description of the predefined message. |
> | `message` | String | Content of the predefined message: list of parts with type and text (JSON array). |
> | `campaigns` | Array of strings | Identifiers of the teams the message belongs to, when restricted. |
> | `created_at` | String | When the record was created, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `updated_at` | String | When the record was last changed, as returned by Fortics (YYYY-MM-DD HH:MM:SS; Fortics stores these record timestamps in UTC). |
> | `extra_fields` | String | Every other field Fortics returned for this record that has no column of its own (JSON object). Credentials (tokens, passwords, keys) are removed. |

## Implementation notes

* **Attendances are finished attendances.** Fortics lists attendance history by date; an attendance in progress appears in **Attendances** (and its messages in **Attendance Messages**) once it finishes. Each sync lists the last 31 days (90 days when Fortics lists attendances by their start date) and loads the attendances that finished since the previous sync (plus the days of **Attendance Lookback**), so attendances that stay open for several days are still captured when they finish. An attendance open for longer than that may not be loaded.
* **Teams are "campaigns" in Fortics.** The team of an attendance is in `campaign_id` and `campaign_name`; the **Teams** table has the same identifiers.
* **Monthly report rows.** The report has names, not identifiers, so each row is identified by month, channel, team, agent login and agent name; two rows with the same names are loaded as one row with their counts added. If the report changes order while it is read, the month is read again; if it keeps changing, the table is not updated in that sync and the sync log says so. The current and the previous month are read again on every sync. If a channel, team or agent is renamed in Fortics during those months, the row under the old name stays in the table: to sum a month, keep only the rows with the latest `extracted_at` of that month.
* **Contacts.** Contacts are read by creation date and checked against the count Fortics reports. Contacts created during the sync are fine. If contacts are deleted while they are read, the connector reads that period again; if they keep disappearing or the list comes back short, the **Contacts** table is not updated in that sync and the sync log says so.
* **Times.** `total_time_seconds`, `handling_time_seconds` and `waiting_time_seconds` are Fortics' TTA, TMA and TME of each attendance, in seconds.
* **Dates.** Dates are loaded as the text Fortics returns. Record timestamps (`created_at`, `updated_at` of the registers) are in UTC; attendance and message times (`finished_at`, `timer_on_wait`, message `created_at`) are in the local time of your instance, named in the `timezone` column of **Attendances**.
* **Attendances without details.** When Fortics no longer keeps the details of an attendance (after the storage period of your plan), the attendance is loaded with the list fields only (`detail_available` = false) and without messages, and the sync log says how many.
* **Permissions.** Before reading anything, the connector checks that the user can read every table you selected. A table the user is not allowed to read, or that your Fortics instance does not have, is skipped with a warning naming it and saying which of the two happened, and the other tables still load; if the user cannot read any selected table, the sync fails with a message.
* **Rate limits.** If Fortics Chat Center asks the connector to slow down, the sync waits and continues, and says so in the sync log.


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