> ## 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.
# Agendor as a data source
> Bring data from Agendor to Nekt.
Agendor is a comprehensive customer relationship management (CRM) platform designed for Brazilian businesses. It provides tools for lead management, deal tracking, contact management, and sales pipeline management with a focus on the Brazilian market and compliance with local regulations.
## Configuring Agendor 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 Agendor option from the list of connectors.
Click **Next** and you'll be prompted to add your access.
### 1. Add account access
You'll need your Agendor API Token for this connection. You can find it in your [Agendor account settings](https://app.agendor.com.br/integracoes) under Menu > Integrações. Once you have it, add the account access and the connector configuration.
The following configurations are available:
* **Auth token**: The token to authenticate against the API service.
* **Start Date**: The earliest date from which records will be synced. This should be in DD-MM-YYYY format. Records created or updated after this date will be extracted from the source.
Once you're done, click **Next**.
### 2. Select streams
Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you.
> 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 a name for each table (which will contain the fetched data) and the type of sync.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** 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](https://docs.nekt.com/runs/scheduling-and-triggers), 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 determine when to execute a [full sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#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.
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.
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
Below you'll find all available data streams from Agendor and their corresponding fields:
Stream for managing team members and user accounts in Agendor.
**Key Fields:**
* `id` - Unique identifier for the user
* `name` - Full name of the user
* `accountId` - Account ID
* `createdAt` - When the user was created
* `isBlocked` - Whether the user is blocked
**Account Information:**
* `account` - Account details including features and capabilities
* `account.features` - Available account features (elasticsearch, new\_funnel, etc.)
**Contact Information:**
* `contact` - Contact details including:
* `email` - Email address
* `work` - Work phone number
* `mobile` - Mobile phone number
* `fax` - Fax number
* `ramal` - Extension number
* `radio` - Radio contact
* `whatsapp` - WhatsApp number
* `facebook` - Facebook profile
* `twitter` - Twitter profile
* `linkedIn` - LinkedIn profile
* `skype` - Skype contact
* `instagram` - Instagram profile
**Team Management:**
* `teams` - Array of teams the user belongs to, including team ID and leadership status
Core stream for deal management and sales pipeline tracking.
**Key Fields:**
* `id` - Unique identifier for the deal
* `title` - Title of the deal
* `description` - Deal description
* `value` - Monetary value of the deal
* `ranking` - Deal ranking (1-5)
* `startTime` - Deal start time
* `endTime` - Deal end time
* `wonAt` - When the deal was won
* `lostAt` - When the deal was lost
* `createdAt` - When the deal was created
* `updatedAt` - When the deal was last updated
**Related Entities:**
* `organization` - Related organization details
* `person` - Related person/contact details
* `author` - User who created the deal
* `owner` - User who owns the deal
* `dealStage` - Current stage in the sales funnel
* `dealStatus` - Current status of the deal
* `lossReason` - Reason for deal loss (if applicable)
**Deal Structure:**
* `parentDealId` - Parent deal ID for deal hierarchies
* `accountId` - Account ID
* `products` - Array of products associated with the deal
* `allowedUsers` - Users with access to this deal
**Custom Fields:**
* `customFields` - Custom field values specific to your organization
Stream for managing company and organization records.
**Key Fields:**
* `id` - Unique identifier for the organization
* `name` - Organization name
* `legalName` - Legal name of the organization
* `email` - Organization email address
* `cnpj` - Brazilian tax identification number
* `description` - Organization description
* `ranking` - Organization ranking
* `website` - Organization website
* `createdAt` - When the organization was created
* `updatedAt` - When the organization was last updated
**Visual Assets:**
* `logo` - Logo URLs in different sizes (full, thumb, thumb\_large)
**Contact Information:**
* `contact` - Complete contact details including phone numbers, social media, and messaging platforms
**Address Information:**
* `address` - Complete address including:
* `country` - Country
* `state` - State/Province
* `city` - City
* `district` - District/Neighborhood
* `streetName` - Street name
* `streetNumber` - Street number
* `postalCode` - Postal/ZIP code
* `additionalInfo` - Additional address information
**Classification:**
* `category` - Organization category
* `leadOrigin` - Lead origin source
* `sector` - Business sector
**Related Data:**
* `products` - Products associated with the organization
* `people` - People/contacts associated with the organization
* `author` - User who created the organization
* `ownerUser` - User who owns the organization
* `allowedUsers` - Users with access to this organization
**Custom Fields:**
* `customFields` - Custom field values specific to your organization
Stream for managing contact information and person records.
**Key Fields:**
* `id` - Unique identifier for the person
* `name` - Full name of the person
* `email` - Email address
* `cpf` - Brazilian individual tax identification number
* `role` - Person's role
* `ranking` - Person ranking
* `description` - Person description
* `birthday` - Birthday
* `avatar` - Avatar URL
* `createdAt` - When the person was created
* `updatedAt` - When the person was last updated
**Related Organization:**
* `organization` - Organization this person belongs to
**Contact Information:**
* `contact` - Complete contact details including phone numbers, social media, and messaging platforms
**Address Information:**
* `address` - Complete address including country, state, city, district, street details, and postal code
**Classification:**
* `category` - Person category
* `leadOrigin` - Lead origin source
**Related Data:**
* `products` - Products associated with the person
* `author` - User who created the person
* `ownerUser` - User who owns the person
* `allowedUsers` - Users with access to this person
**Custom Fields:**
* `customFields` - Custom field values specific to your organization
Stream for managing activities, tasks, and appointments.
**Key Fields:**
* `id` - Unique identifier for the task
* `text` - Task description
* `type` - Task type
* `dueDate` - Task due date
* `finishedAt` - When the task was completed
* `createdAt` - When the task was created
* `updatedAt` - When the task was last updated
**Assignment:**
* `user` - User assigned to the task
* `assignedUsers` - Array of users assigned to the task
* `finishedBy` - User who completed the task
**Related Entities:**
* `organization` - Related organization
* `person` - Related person/contact
* `deal` - Related deal
**Metrics:**
* `metrics` - Array of task metrics including metric ID, name, and value
Stream for managing sales funnels and their configuration.
**Key Fields:**
* `id` - Unique identifier for the funnel
* `name` - Funnel name
* `initials` - Funnel initials
* `color` - Funnel color
* `sequence` - Funnel sequence order
* `default` - Whether this is the default funnel
**Deal Stages:**
* `dealStages` - Array of deal stages in this funnel, including:
* `id` - Stage ID
* `name` - Stage name
* `sequence` - Stage sequence within the funnel
Stream for managing categories used to classify organizations and people.
**Key Fields:**
* `id` - Unique identifier for the category
* `name` - Category name
Stream for managing business sectors used to classify organizations.
**Key Fields:**
* `id` - Unique identifier for the sector
* `name` - Sector name
Stream for managing products and services offered.
**Key Fields:**
* `id` - Unique identifier for the product
* `name` - Product name
* `code` - Product code
* `price` - Product price
* `active` - Whether the product is active
* `createdAt` - When the product was created
## Skills for agents
Agendor connector documentation as plain markdown, for use in AI agent contexts.