Skip to main content
Moskit is a customer service and support management platform that helps businesses handle customer inquiries and support requests efficiently. It provides tools for ticket management, customer communication, and service analytics to improve customer satisfaction and support operations.

​
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. The following configurations are available:
  • API Key: The key to authenticate against the API service. This token can be obtained from the Moskit CRM on Marketplace > Public API.
  • Enable deal notes stream: (Default: false) Enables the deal_notes stream: the notes written on each deal, which are not the same as the notes and doneNotes columns of the activities stream. Moskit exposes no field recording when a note was written, so this stream cannot run incrementally and performs an additional API call for every deal that has notes, on every run. Enable only if necessary, since it significantly increases the extraction time.
  • Stage movements lookback days: (Default: 1) Advanced: number of days re-checked before the saved bookmark when selecting which deals the deal_stage_movements stream visits. Movements are deduplicated by primary key, so a wider window costs extraction time but never duplicates rows.
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 - 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. 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. 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 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.

​
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. Streams marked optional are only discovered when the corresponding setting is enabled.

​
Fields by stream

Below you’ll find the available data streams from Moskit and their corresponding fields:
Stream for retrieving activities data.
Stream containing the different types of activities available in Moskit.
Stream for retrieving companies data.
Stream for retrieving contacts data.
Stream containing the custom fields configured in the Moskit workspace.
Stream containing the available options for dropdown or multiple-choice custom fields.
Stream containing the notes written against a deal. This stream is only available when “Enable deal notes stream” is turned on in the source configuration.
Stream containing the stage changes (movements) of a deal.
Stream for retrieving deals (opportunities) data.
Stream containing the reasons why a deal was marked as lost.
Stream containing the sales pipelines configured in Moskit.
Stream for retrieving projects data.
Stream containing business proposals sent to customers.
Stream containing the stages within pipelines.
Stream containing step configurations, typically linked to boards.
Stream containing organizational teams.
Stream containing the users registered in the Moskit workspace.

​
Skills for agents

Download Moskit skills file

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