Configuring Moskit as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Moskit 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 authorize Nekt to access your Moskit data. Check Moskit documentation to discover where you can generate the API Key for the connection. 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: Moskit only allows FULL_TABLE synchronization. Every time the extraction happens, we’ll get the current state of the data. Read more about Sync Types here.
4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters. You can inform things like what data it brings, to which team it belongs, etc. 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. Given that Moskit only allows Full Syncs, this is not necessary.
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.Streams and Fields
Below you’ll find the available data streams from Moskit and their corresponding fields:Activities
Activities
Stream for retrieving activities data.
Activity Types
Activity Types
Stream containing the different types of activities available in Moskit.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the activity type |
name | String | Name of the activity type |
Companies
Companies
Stream for retrieving companies data.
Contacts
Contacts
Stream for retrieving contacts data.
Custom Fields
Custom Fields
Stream containing the custom fields configured in the Moskit workspace.
| Field | Type | Description |
|---|---|---|
id | String | Unique identifier for the custom field |
name | String | Name of the custom field |
active | Boolean | Indicates if the custom field is currently active |
priority | Integer | Display priority or order |
type | String | Data type of the field |
module | String | The module the field belongs to |
pipelines | Array | List of associated pipeline objects |
Custom Field Options
Custom Field Options
Stream containing the available options for dropdown or multiple-choice custom fields.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the option |
label | String | Display label of the option |
custom_field_id | String | Unique identifier of the parent custom field |
Deals
Deals
Stream for retrieving deals (opportunities) data.
Lost Reasons
Lost Reasons
Stream containing the reasons why a deal was marked as lost.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the lost reason |
name | String | Description or name of the lost reason |
pipelines | Array | List of associated pipeline objects |
Pipelines
Pipelines
Stream containing the sales pipelines configured in Moskit.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the pipeline |
name | String | Name of the pipeline |
priority | Integer | Display priority or order |
Projects
Projects
Stream for retrieving projects data.
Proposals
Proposals
Stream containing business proposals sent to customers.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the proposal |
name | String | Name of the proposal |
pdf | String | Link or reference to the generated PDF |
dateCreated | String | Date and time when the proposal was created |
createdBy | Object | Information about the user who created the proposal |
deal | Object | Associated deal information |
Stages
Stages
Stream containing the stages within pipelines.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the stage |
name | String | Name of the stage |
priority | Integer | Display priority or order |
description | String | Detailed description of the stage |
pipeline | Object | Associated pipeline information |
Steps
Steps
Stream containing step configurations, typically linked to boards.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the step |
name | String | Name of the step |
priority | Integer | Display priority or order |
board | Object | Associated board information |
Teams
Teams
Stream containing organizational teams.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the team |
name | String | Name of the team |
parent | Object | Information about the parent team, if applicable |
Users
Users
Stream containing the users registered in the Moskit workspace.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier for the user |
name | String | Full name of the user |
username | String | Username for login |
active | Boolean | Indicates if the user account is active |
levelConfig | Boolean | Configuration access permission |
levelExport | Boolean | Export access permission |
levelBulk | Boolean | Bulk operation access permission |
levelDelete | Boolean | Deletion access permission |
levelView | String | View access level scope |
levelEdit | String | Edit access level scope |
jobTitle | String | User’s job title |
team | Object | Associated team information |
timezone | Object | User’s timezone settings |
picture | String | URL of the user’s profile picture |
phones | Array | List of the user’s phone numbers |
primaryPhone | Object | The user’s primary phone number |
defaultPipeline | Object | User’s default pipeline |
defaultBoard | Object | User’s default board |
defaultDashboard | Object | User’s default dashboard |
dateCreated | String | Date and time when the user was created |
Skills for agents
Download Moskit skills file
Moskit connector documentation as plain markdown, for use in AI agent contexts.