Source connector

Moskit CRM connector

Moskit CRM integration for databases, warehouses and BI tools

Sales CRM for Brazilian inside-sales teams. Datrise captures Moskit CRM entities such as contacts, companies, deals, funnel stages, tasks and sales goals, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Moskit CRM (Ollow) API v2 authenticates with API key, and Moskit CRM caps calls at 6 requests/second and 240 requests/minute per API key (HTTP 429 on either limit; tracked via X-RateLimit-Limit-Second / X-RateLimit-Limit-Minute response headers).

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `moskit_contacts`) with a schema derived from the Moskit CRM API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Moskit CRM pipeline page, and join the waitlist to get the Moskit CRM connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Moskit CRM data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
contacts	moskit_contacts	Upsert by primary key, incremental on updated-at
companies	moskit_companies	Upsert by primary key, incremental on updated-at
deals	moskit_deals	Upsert by primary key, incremental on updated-at
funnel stages	moskit_funnel_stages	Upsert by primary key, incremental on updated-at
tasks	moskit_tasks	Upsert by primary key, incremental on updated-at
sales goals	moskit_sales_goals	Upsert by primary key, incremental on updated-at

Moskit CRM API: setup facts for the connector

Verified against the vendor documentation on 2026-09-21. Unknown values are left blank rather than guessed.

API	Moskit CRM (Ollow) API v2
Authentication	API key — A per-account API key generated under Marketplace > API pública in the app is sent on every request in an `apikey` header; a missing or invalid key returns HTTP 401 with `{"message":"Invalid authentication credentials"}`.
Pagination	offset — Default `start` (offset, default 0) + `quantity` (default 10, max 50) paging only works while `start + quantity` stays under 10,000; beyond that the API returns HTTP 422 and callers must switch to the `nextPageToken` cursor returned in the `X-Ollow-Listing-Next-Page-Token` response header.
Rate limit	6 requests/second and 240 requests/minute per API key (HTTP 429 on either limit; tracked via X-RateLimit-Limit-Second / X-RateLimit-Limit-Minute response headers)
Incremental cursor	Not published
Webhooks	No
Bulk export	No
Deletes detectable	No — No soft-delete flag or deleted-records endpoint is documented; a record removed via `DELETE /v2/contacts/{id}` (or deleted in the app) simply stops appearing in `GET /v2/contacts`, so reconciliation requires diffing full ID snapshots.

Official API reference

What bites when replicating Moskit CRM

Moskit rebranded to 'Ollow' in September 2026 (repositioning around WhatsApp-first AI conversational sales); the API v2 reference and base URL now live under the Ollow name (`api.ms.prod.ollow.services`) even though the product is still marketed as Moskit CRM at moskitcrm.com.
Deep pagination is capped: `start + quantity` must stay under 10,000 records or the API returns HTTP 422 ('Preview invalid for index records greater than 10000'); paging past that point requires the `nextPageToken` cursor instead of `start`.
List responses default to `quantity=10` and cap at `quantity=50` per page — an integration that doesn't raise `quantity` burns far more requests than necessary against the 6 req/s ceiling.
Related-entity arrays embedded on a record (e.g. a company's `contacts`, a deal's `activities`) are hard-capped at 1,000 elements each; accounts with larger related sets need the dedicated entity endpoints rather than the embedded array.

Compare this against every other documented API

Popular destinations for Moskit CRM

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Moskit CRM connector FAQ

What Moskit CRM data does the connector extract?: 6 objects: contacts, companies, deals, funnel stages, tasks and sales goals. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Moskit CRM integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Moskit CRM data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Moskit CRM → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Moskit CRM pipeline with guided onboarding

Join the waitlist to get priority access for Moskit CRM integrations with guided setup, schema-aware mapping, and production-grade incremental sync.