Skip to main content
Atendare is a customer service and support management platform designed to help businesses handle customer inquiries, support tickets, and service requests efficiently. It provides tools for ticket management, customer communication, and service analytics to improve customer satisfaction.

​
Configuring Atendare as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Atendare option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide your Atendare credentials to authorize Nekt to access your data. The following configurations are available:
  • Access Token: The token to authenticate against the API service. Get in touch with Atendare support team to get a token for your account. For detailed instructions, check their documentation.
  • Start Date: The date of the first record you want to sync with. We will extract every record created or updated after this. Format: YYYY-MM-DD.
Under Advanced settings, you can optionally turn on the file streams:
  • Enable contract files stream: When enabled, the source adds a contract_files stream that downloads every contract’s PDF document and uploads it to a Nekt volume. This makes extractions slower and heavier, since each PDF is downloaded from Atendare and re-uploaded to Nekt. Only enable this if you need the contract files stored in a Nekt volume.
  • Contract Files Volume: The Nekt volume to upload contract PDFs to. Required when the contract files stream is enabled.
  • Enable proposal files stream: When enabled, the source adds a proposal_files stream that downloads every proposal’s PDF document and uploads it to a Nekt volume. Same performance caveat as above. Only enable this if you need the proposal files stored in a Nekt volume.
  • Proposal Files Volume: The Nekt volume to upload proposal PDFs to. Required when the proposal files stream is enabled.
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.
If you don’t see a stream you were expecting to find, please check if your access key has access to it. If that’s not the issue, then it’s probably because we still haven’t implemented it. Feel free to get in touch and request it!
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 - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
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, 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.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
When you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Skills for agents

Download Atendare skills file

Atendare connector documentation as plain markdown, for use in AI agent contexts.

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

​
Streams and Fields

Below you’ll find the available documented data streams from Atendare and their key fields:
Stream containing deal records. This serves as the parent stream for proposals and contracts.
Stream for retrieving budgets/proposals associated with your Deals (/deals/{deal_id}/budgets).Key Fields:
Stream for retrieving agreements/contracts associated with your Deals (/deals/{deal_id}/agreements).Key Fields:
PDF documents of each deal’s contracts, downloaded through /deals/{deal_id}/agreements/{contract_id}/pdf and uploaded to a Nekt volume. Child stream of Contracts, only registered when Enable contract files stream is on. It emits one metadata record per uploaded file so the original link to volume file mapping can be rebuilt downstream.Key Fields:
PDF documents of each deal’s proposals, downloaded through /deals/{deal_id}/budgets/{proposal_id}/pdf and uploaded to a Nekt volume. Child stream of Proposals, only registered when Enable proposal files stream is on. It emits one metadata record per uploaded file so the original link to volume file mapping can be rebuilt downstream.Key Fields:

​
Data Model

The following diagram illustrates the relationships between deals, their proposals and contracts, and the optional file streams:

​
Implementation Notes

​
Incremental Sync Behavior

  • Child Streams (Proposals & Contracts): These streams act as child streams to the Deals stream. During incremental runs, the connector only traverses the subset of deals emitted by the parent.
  • To prevent data loss from untouched deals, proposals and contracts are strictly configured as INCREMENTAL streams using update_date as the replication key (and id as the primary key). This setup guarantees the target destination handles the sync as a merge/upsert instead of a full table replacement.
  • API Limitations: Note that the specific endpoints for proposals and contracts do not natively support query parameters for filtering by date or paging. Records arrive grouped per deal and are not globally sorted by update_date. The replication key is set purely to dictate the target’s merge behavior.

​
Sync Behaviors

  • Full Sync Integration: When a stream’s sync method is forced to FULL_TABLE (such as during a manual resync or an Additional Full Sync event), the connector automatically identifies this and bypasses any existing incremental date filters. This ensures all historical records are retrieved unfiltered without encountering API parameter errors.

​
File Streams Behavior

  • Opt-in only: The contract_files and proposal_files streams are not registered unless their corresponding Enable … files stream flag is turned on in the source configuration, so accounts that don’t need volume uploads are unaffected (no extra catalog entries, no per-record child syncs).
  • Why they exist: Atendare hosts each generated document behind a public link (https://web.atendare.com/public/docs/...) that stops working if the account is decommissioned. The file streams preserve the documents in a Nekt volume and emit the original link alongside the _nekt_file_* columns so the old link to volume file mapping can be rebuilt downstream (for example, to regenerate links in a CRM).
  • Performance impact: Enabling these streams makes extractions slower and heavier. The connector downloads each PDF (which can reach several MB) individually from the API’s /pdf endpoints and uploads it to the designated Nekt volume.
  • Deduplication: Uploaded files use a deterministic volume file name (contract_{id}.pdf or proposal_{id}.pdf), so subsequent runs overwrite the previous file in place instead of creating duplicates.
  • Replication strategy: These are child streams of contracts and proposals, which are themselves incremental, so each run only downloads and uploads PDFs for the subset of contracts or proposals emitted by the parents. Like their parents, they use update_date as the replication key with contract_id/proposal_id as primary key so the destination merges records instead of replacing the table.
  • Skipped records: Contracts or proposals without a generated document (no link) are skipped, and so is any record whose PDF endpoint answers with a JSON error body instead of a PDF. These skips are logged and do not fail the run.