Resources · Zapier integration

Moskit Zapier integrationAutomate Moskit with Zapier.

The Moskit Zapier integration gives you 24 triggers, 29 actions and 7 searches. Every trigger is instant, so the free plan never slows a Zap down. Here is what each operation does in your CRM, what it costs in tasks, and where it trips.

See the 60 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Moskit Zapier integration really does

Moskit is a CRM built around contacts, companies, deals and projects. The integration plugs it into Zapier, so it can sit inside a Zap: an automation with one starting event and one or more steps after it. Something happens in Moskit or in another tool, and Zapier writes the follow-up for you, with no copy and paste.

Three results you can build from the operations that exist. A project opened from a won deal: Deal Won starts the Zap and Create Project sets up the delivery side. A deal born from a form: a new form answer goes through Search Contact, then Create Deal opens the deal in the pipeline. A handover that leaves a trace: Deal Responsible Changed fires when a deal changes hands, and Add Deal Note records it on the deal.

What Zapier does not do here. None of the 29 actions deletes anything: you can archive a project, mark a deal as lost or update a record, but removing a contact or a company stays a job for Moskit itself. There is no trigger for a new product or a new note either, so those events cannot start a Zap. And many actions work on a record that already exists, which means the Zap has to find it first with one of the 7 searches, or receive its ID from the trigger.

If you are still choosing a tool, see our Make vs Zapier comparison and our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary, in one minute

Eight words come back all over this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that creates, updates or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment the event happens, as on Moskit.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up a record that already exists in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it then needs a paid plan.
Cost

What a Moskit Zap really costs

Moskit is not a premium app on Zapier (an app kept for paid plans), so it runs on the free plan. The bill is counted in tasks.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, unlimited two-step Zaps
  • TriggerNever costs a task
  • Instant triggersAll 24, the grid does not apply

The trigger never costs a task. Each action that succeeds counts as one, so a three-action Zap uses three times what a one-action Zap uses, and an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A filter, a search or a second action makes the Zap multi-step, which needs a paid plan. Zapier publishes the polling grid below for apps that are checked on a timer; it does not apply to Moskit, whose 24 triggers are all instant.

Connect

Connect Moskit to Zapier in three steps

  1. 01

    Open your Apps page

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Moskit account linked once, then reused by every step that talks to Moskit.

  2. 02

    Find Moskit

    Type Moskit in the search box of the dialog, pick it in the results, then click Add connection. A new tab opens on the Moskit sign-in screen, where the last step happens.

  3. 03

    Sign in and grant access

    Log in to Moskit in that tab and grant Zapier access to the account. You need an account on Moskit, plus read or write access on anything you do not own yourself and want the Zap to touch.

First Zap

Your first Moskit Zap: open a project when a deal is won

GoalWhen a deal is won in Moskit, check that it meets the condition you choose, then create the delivery project in Moskit.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose Moskit as the app and Deal Won as the trigger event, then select the Moskit connection you added earlier.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent won deals of the connected account. Pick a real one, so the next steps are mapped on actual data.

  3. 03

    Add a filter

    Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, the value to compare. A filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Create Project

    Add Moskit with Create Project and fill the form with what the won deal carries. Check at test which fields the editor asks for.

  5. 05

    Test, then publish

    Run each step once and read what came back before going further. When the output looks right, publish the Zap to switch it on for the next deals won.

Triggers

Moskit triggers on Zapier

24 events start a Zap when something happens in Moskit, and 24 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Activity Completion Attemp

Instant trigger

In Zapier“Triggers when activity is try.”

Zapier lists this trigger as Activity Completion Attemp, spelling included. Its official description is a handful of words and never says which gesture in Moskit sends the event, so this page cannot tell you either. Run a test and read what comes back before you build anything on it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the test has shown you which Moskit event it follows, and that exact event should start a Zap.
Watch out
it is a separate trigger from Activity Completed; do not assume the two send the same events.
2

New Activity Created

Instant trigger

In Zapier“Triggers when a new activity is created.”

Fires each time a new activity lands in Moskit, whoever created it. The Zap receives that activity and can copy it to a calendar, a shared list or a message for the team.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every scheduled meeting in Moskit should also appear in the calendar your team already reads.
Watch out
it only sees activities created after the Zap is published, so the ones already planned stay where they are.
3

Activity Completed

Instant trigger

In Zapier“Triggers when a new activity is done.”

Reacts when an activity is marked as done in Moskit. The finished activity becomes the starting point of whatever should happen next, a follow-up, a note elsewhere or a line in a report.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
once an activity is done, the next one should be planned without anyone thinking about it.
Watch out
if the Zap creates activities in Moskit too, a Zap that writes where its trigger watches can set itself off again.
4

Activity Responsible Changed

Instant trigger

In Zapier“Triggers when activity responsible is changed.”

Each time the responsible of an activity changes in Moskit, the Zap starts. Zapier documents nothing beyond that, so the test is where you see what reaches the Zap along with the activity.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a reassigned activity should leave a trace in another tool, such as a row in a shared sheet.
Watch out
map only what you saw arrive at test into the next step.
5

Activity Updated

Instant trigger

In Zapier“Triggers when a new activity is updated.”

Follows any edit made to an existing activity in Moskit. The Zap starts with the updated version of the activity; which details come with it, the test shows.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a rescheduled meeting has to move in an outside calendar as well.
Watch out
every kind of edit starts the Zap, so put a filter after the trigger if only some changes matter; a filter needs a paid plan.
6

New Company Created

Instant trigger

In Zapier“Triggers when a new company is created.”

Kicks off the Zap each time a company is added to Moskit. The new company record travels to the next step, ready to be copied into a billing tool, a spreadsheet or a mailing list.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every new company in the CRM should also exist in another tool you use.
Watch out
a bulk import of companies can send a huge batch at once, and Zapier's flood protection may hold it back.
7

Company Responsible Changed

Instant trigger

In Zapier“Triggers when company responsible is changed.”

A company whose responsible changes in Moskit sets this trigger off, and the Zap starts with that company. Read the test result to see what comes with it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every reassigned company should be logged in a spreadsheet you review.
Watch out
only reassignments made after the Zap is published count; the current split of accounts is not replayed.
8

Company Updated

Instant trigger

In Zapier“Triggers when a new company is updated.”

Starts the Zap when the details of a company change in Moskit. The edited company arrives in the Zap so a copy kept elsewhere can follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a copy of each company lives in another tool and should stay in line with the CRM.
Watch out
a Zap that writes the same company back into Moskit can restart itself, so check what your trigger watches.
9

New Contact Created

Instant trigger

In Zapier“Triggers when a new contact is created.”

Fires on every contact added to Moskit, whatever added it. The contact record is handed to the next step, ready for a newsletter tool, a sheet or a welcome email.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
new contacts should join your mailing list without anyone exporting them.
Watch out
contacts created by another Zap start this one too, so check your Zaps do not feed each other in a loop.
10

Contact Responsible Changed

Instant trigger

In Zapier“Triggers when contact responsible is changed.”

Runs when the responsible of a contact changes in Moskit. The contact reaches the Zap, ready for the next step; the test shows what arrives with it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each change of hands on a contact should be recorded in another tool you follow.
Watch out
check at test what the event brings back before you map it anywhere.
11

Contact Updated

Instant trigger

In Zapier“Triggers when a new contact is updated.”

Reacts to edits on an existing contact in Moskit, whatever was changed. The Zap starts with the contact as it now stands.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your email tool should always hold the same address as the CRM.
Watch out
many small edits mean many runs, and each action that succeeds is a task; a filter on the field you care about lets only some edits through, and it needs a paid plan.
12

New Deal Created

Instant trigger

In Zapier“Triggers when a new deal is created.”

Opens the Zap each time a deal is created in Moskit. The new deal, with what it carries, becomes data for the next step: a message, a row in a forecast sheet or a task elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the team wants a message in its chat tool for every new deal.
Watch out
deals opened before the Zap goes live are not picked up later.
13

Deal Lost

Instant trigger

In Zapier“Triggers when a deal is lost.”

Fires when a deal is marked as lost in Moskit. The Zap gets the closed deal, which is the right moment to record why, to warn someone or to plan a later follow-up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every lost deal should leave a row in a spreadsheet you review.
Watch out
every lost deal starts the Zap; a filter keeps only the ones you want, and it needs a paid plan.
14

Deal Reopened

Instant trigger

In Zapier“Triggers when a deal status is open.”

Its label says Deal Reopened, and Zapier's description only says it fires when a deal status is open. Nothing more is documented, so what counts as that event in your account is something the test shows you, not this page.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you need a Zap on that status event and have checked at test which deals it sends.
Watch out
check at test that it does not also fire on brand new deals in your account.
15

Deal Responsible Changed

Instant trigger

In Zapier“Triggers when a deal responsible is changed.”

Watches each deal for a change of responsible in Moskit. When one happens, the Zap starts with that deal, and the test shows what it carries.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a handover should leave a note on the deal through Add Deal Note.
Watch out
if the same Zap also changes the responsible person, it writes where its trigger watches and can restart itself.
16

Deal Stage Changed

Instant trigger

In Zapier“Triggers when a deal stage is changed.”

Follows deals through your pipeline: each move from one stage to another in Moskit starts the Zap with the deal and its new stage.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
reaching one given stage should create an item in another tool.
Watch out
every stage move counts, forward or backward; a filter keeps only the move you want, and it needs a paid plan.
17

Deal Updated

Instant trigger

In Zapier“Triggers when a deal is updated.”

Reacts to any edit on an existing deal in Moskit, whatever was changed. The Zap starts with the deal as it reads after the change.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a sheet that tracks open deals should follow each change made in the CRM.
Watch out
check at test whether stage moves or wins also start this trigger, so two Zaps do not handle the same change twice.
18

Deal Won

Instant trigger

In Zapier“Triggers when a deal is won.”

Fires the moment a deal is marked as won in Moskit. It is a clear point to hand a deal over to the next part of your process: the Zap starts with the won deal and everything it carries.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a won deal should open its project and warn the people who follow it next.
Watch out
only deals won after the Zap is published count; past wins are not sent.
19

Project Archived

Instant trigger

In Zapier“Triggers when a project is archived.”

Closing a project in Moskit by archiving it starts the Zap. The archived project is handed on, so the other tools that track it can close their side as well.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an archived project should be marked as finished in the spreadsheet where you follow projects.
Watch out
a project brought back later starts Project Unarchived, not this trigger, so plan both if the sheet must stay exact.
20

New Project Created

Instant trigger

In Zapier“Triggers when a new project is created.”

Every new project that appears in Moskit sets this off, whether someone created it by hand or a Zap did. The project becomes the input of your next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each new project should get its own folder or board in the tool the team works in.
Watch out
if another Zap creates projects from won deals, this trigger fires on those too; check that the chain does not loop back.
21

Project Responsible Changed

Instant trigger

In Zapier“Triggers when the responsible project is changed.”

A project whose responsible changes in Moskit starts this one, and the project is handed to the next step. What comes with it is for the test to show.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a project changing hands should update the row that tracks it in a sheet.
Watch out
read the test result before mapping; only what it shows is safe to use.
22

Project Step Changed

Instant trigger

In Zapier“Triggers when the step project is changed.”

Follows a project from one step to the next in Moskit. Each change of step starts the Zap with the project and the step it has just reached.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
moving a project to one given step should send an update from your email tool.
Watch out
every step change starts the Zap; add a filter on the step if only one of them should send something.
23

Project Unarchived

Instant trigger

In Zapier“Triggers when a project is unarchived.”

Fires when an archived project comes back to life in Moskit. The Zap starts with the restored project, ready to reopen it in the tools that had closed it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a project restarted after a pause should show as active again in your tracking sheet.
Watch out
it is the mirror of Project Archived; build both Zaps together or the outside view drifts.
24

Project Updated

Instant trigger

In Zapier“Triggers when a project is updated.”

Any edit on an existing Moskit project counts here, whatever was changed. The Zap starts with the project as it now stands.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
another tool that tracks your projects should follow the changes made in the CRM.
Watch out
check at test whether archiving or step changes also count as updates here, to avoid handling one change in two Zaps.
Actions

Moskit actions on Zapier

Moskit gives you 29 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Activity

Action

In Zapier“Create new Activity.”

Schedules a new activity in Moskit from what the Zap carries.

When to use it
an event added to your calendar should also exist as an activity in the CRM.
Watch out
if the trigger watches new activities in Moskit, this action writes where it looks and can restart the Zap.
2

Complete Activity

Action

In Zapier“Done activity.”

Marks an activity as done in Moskit from a signal that comes from somewhere else.

When to use it
an event recorded in another tool should close the matching activity in the CRM.
Watch out
any Zap built on Activity Completed starts too; check the chain before publishing.
3

Change Activity Responsible

Action

In Zapier“Change responsible of activity.”

Passes an activity to another user in Moskit.

When to use it
an activity should go to the user named in a shared spreadsheet.
Watch out
the activity must be known to the Zap first, from the trigger or from Search Activity.
4

Update Activity

Action

In Zapier“Update a activity.”

Changes an activity already planned in Moskit.

When to use it
an event moved in your calendar should move in the CRM as well.
Watch out
Search Activity is the way to find the activity first when only its details are known.
5

Create Company

Action

In Zapier“Creates a new company.”

Creates a company record in Moskit from the data an earlier step hands over.

When to use it
a company added in another tool should exist in the CRM too.
Watch out
run Search Company before it if the same company could arrive twice, otherwise you may end up with two records.
6

Add Company Note

Action

In Zapier“Add note in Company.”

Pins a note on a company record in Moskit, visible to anyone who opens the account.

When to use it
an item closed in another tool should leave a short trace on the matching company.
Watch out
map a clear text into the note; a raw dump of fields is hard to read in the CRM.
7

Change Company Responsible

Action

In Zapier“Change responsible of Company.”

Reassigns a company to another Moskit user.

When to use it
a company flagged in another tool should move to another owner.
Watch out
check at test that the user is found by Search User before this step, rather than typed by hand.
8

Update Company

Action

In Zapier“Update a company.”

Rewrites the details of a company already in Moskit. Search Company can bring that company into the Zap first when the trigger comes from another tool.

When to use it
details corrected in another tool should follow in the CRM.
Watch out
check at test what the record looks like in Moskit afterwards.
9

Create Contact

Action

In Zapier“Creates a new contact.”

Adds a new person to Moskit from the data an earlier step brings, such as a form answer or a sign-up.

When to use it
people who fill in a form should land in the CRM without retyping.
Watch out
when the person may already exist, Search Contact with its create option checks first.
10

Add Contact Note

Action

In Zapier“Add note in Contact.”

Writes a note on a contact in Moskit, a quick way to keep context next to the person.

When to use it
each form answer should leave its content as a note on the contact who sent it.
Watch out
the contact has to be found first; Search Contact before this step does that job.
11

Change Contact Responsible

Action

In Zapier“Change the responsible of Contact.”

Gives a contact a new responsible user in Moskit.

When to use it
a contact who answers a form should move to the user named in it.
Watch out
a Zap watching Contact Responsible Changed will start after this action, which is useful or a loop depending on what it does.
12

Update Contact

Action

In Zapier“Action to update a contact.”

Changes the details of an existing contact in Moskit with fresh data from another tool.

When to use it
an address changed in your email tool should reach the CRM.
Watch out
if a Zap watching Contact Updated also runs, the two can feed each other; check what each trigger watches.
13

Create Deal

Action

In Zapier“Create a new Deal.”

Opens a new deal in Moskit from what the earlier steps carry.

When to use it
a new form answer should start its own deal in the pipeline.
Watch out
check at test which fields the form asks for before mapping anything.
14

Lose Deal

Action

In Zapier“Lost Deal.”

Closes a deal as lost in Moskit without anyone opening the CRM.

When to use it
a contact who declines through a form should see their deal closed as lost.
Watch out
make sure the Zap finds the right deal, with Search Deal if needed, since a wrong match closes the wrong opportunity.
15

Add Deal Note

Action

In Zapier“Create note in deal.”

Adds a note to a deal in Moskit, so its history keeps what happened outside the CRM.

When to use it
an event recorded in another tool should be logged on the deal it belongs to.
Watch out
without the deal from the trigger or from Search Deal, the step has nothing to attach the note to.
16

Change Deal Responsible

Action

In Zapier“Change responsible of deal.”

Hands a deal to another user of Moskit.

When to use it
deals coming from a form should go to the user named in one of its fields.
Watch out
Search User can find the user to assign; check at test what value the field expects.
17

Change Deal Stage

Action

In Zapier“Change stage of the Deal.”

Moves a deal to another stage of your Moskit pipeline from an event elsewhere.

When to use it
an event recorded in another tool should push the deal one stage ahead.
Watch out
any Zap built on Deal Stage Changed will start too; check that the two do not answer each other.
18

Update Deal

Action

In Zapier“Update a deal.”

Edits an existing deal in Moskit with values from another tool.

When to use it
a value revised in another tool should update the deal it belongs to.
Watch out
Search Deal can bring the deal into the Zap when the trigger comes from outside Moskit.
19

Won Deal

Action

In Zapier“Won Deal.”

Marks a deal as won in Moskit from an outside signal.

When to use it
a confirmation recorded in another tool should close the matching deal as won.
Watch out
any Zap built on Deal Won starts from this, so a won deal created this way also opens its project if such a Zap exists.
20

Create Product

Action

In Zapier“Create a new Product.”

Adds an item to the product catalog of Moskit, the list your deals can draw from.

When to use it
a new item added to a spreadsheet of products should appear in the CRM too.
Watch out
Search Product can find an existing item first, which avoids filling the catalog with copies.
21

Add Product to Deal

Action

In Zapier“Links a new product to a deal.”

Links a product to a deal in Moskit, so the deal shows what is actually being sold.

When to use it
a new row in another tool should attach the right product to the matching deal.
Watch out
the Zap needs both the deal and the product; Search Deal and Search Product can bring them in earlier steps.
22

Update Product

Action

In Zapier“Update a product.”

Changes a product in the Moskit catalog.

When to use it
a product edited in a spreadsheet should change in the CRM without a second edit.
Watch out
Search Product brings the right item in first; check at test that it picks the one you mean.
23

Archive Project

Action

In Zapier“Archive a Project.”

Moves a project to the archive in Moskit, the closest thing to removing it that this integration offers.

When to use it
a project marked as closed in another tool should leave the active list in the CRM.
Watch out
archiving is not deleting; Unarchive Project can bring the project back.
24

Create Project

Action

In Zapier“Create a new Project.”

Sets up a new project in Moskit without anyone opening the CRM.

When to use it
a won deal should open a project, so nobody creates it by hand.
Watch out
projects created this way also start any Zap that watches New Project Created.
25

Add Project Note

Action

In Zapier“Add note in Project.”

Records a note on a project in Moskit, next to its steps and its owner.

When to use it
an answer sent through a form should be stored on the project concerned.
Watch out
Search Project finds the project first when the trigger comes from another tool.
26

Change Project Responsible

Action

In Zapier“Change responsible of Project.”

Puts another Moskit user in charge of a project.

When to use it
a project reaching a given step should move to another user.
Watch out
Search User and Search Project together bring both values; check at test that each finds one record.
27

Change Project Step

Action

In Zapier“Change step of project.”

Sets a project to another step in Moskit, so its progress matches what happened elsewhere.

When to use it
a row marked as done in a spreadsheet should move the project to the next step.
Watch out
check at test how the step is chosen in the form before mapping it from another tool.
28

Unarchive Project

Action

In Zapier“Unarchive a Project.”

Brings an archived project back to the active list in Moskit.

When to use it
a project restarted after a pause should show as active again.
Watch out
the project must be identified first; Search Project can find it when the trigger comes from another tool.
29

Update Project

Action

In Zapier“Update a project.”

Edits a project that already exists in Moskit.

When to use it
a change made in another tool should be reflected on the project.
Watch out
a Zap that starts on Project Updated and runs this action writes where its trigger watches.
Searches

Moskit searches on Zapier

7 search steps look for data that already exists in Moskit, so a later step can use it.

A search step finds a record that already exists in Moskit and hands it to the steps that follow. In the editor, the searches sit at the bottom of the Action event list, under the SEARCH heading. Six of the seven Moskit searches can also create the record when nothing matches; Search User cannot. Whether a search wants the exact value or something close is up to Moskit, so check it at test.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns the search into a find-or-create. The setting above then disappears, and the step asks for the fields needed to create the missing record.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a Moskit Zap breaks

Zapier attaches no help article to Moskit, so the cases below are the general Zapier limits that apply to it.

Four general cases are worth knowing before you publish. For anything else, see our Zapier troubleshooting guide.

  • Past records are not picked up

    A Zap only reacts to what happens after you switch it on. Deals, contacts or projects that already existed stay out; moving the backlog is a separate job.

  • A Zap that restarts itself

    A Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your task count.

  • A big import gets held back

    When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back.

  • A search that finds nothing

    Left on its default setting, a search that finds no match stops the Zap at that step, and the steps that depended on it are skipped.
Need help

Need help automating Moskit with Zapier?

A person reads every message.

FAQ

Moskit Zapier integration: common questions

01Is the Moskit Zapier integration free?
Partly. Moskit is not a premium app on Zapier, so the free plan accepts it, with 100 tasks a month and unlimited Zaps of two steps each: one trigger and one action. A Zap that opens a project for every won deal fits. Anything longer does not: none of the seven searches, no filter and no second action can be added on the free plan, because each of them makes the Zap multi-step, which needs a paid plan. All 24 triggers are instant on every plan.
02How many tasks does a Moskit Zap use?
One task for each action that succeeds, nothing for the trigger. A Zap that opens a project for every won deal uses one task per win. If it also adds a note to the deal, every win costs two, and a third action would make it three. An action that fails is not counted against your plan. Keep an eye on busy triggers such as Contact Updated, since every edit can start a run.
03Does Moskit trigger Zaps in real time?
Yes. All 24 triggers are instant: Moskit tells Zapier the moment the event happens, so the Zap starts right away on any plan. The polling grid published by Zapier does not apply to them. In the editor, a Zap built on an instant trigger shows a lightning bolt. The polling interval only matters for apps checked on a timer, which Moskit is not, so a free plan and a paid plan start a Moskit Zap the same way.
04What does it take to connect Moskit to Zapier?
An account on Moskit, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once from the Apps page of Zapier: click + Add connection, search Moskit, click Add connection, then sign in to Moskit in the tab that opens and grant access. Every Moskit step of every Zap then reuses that connection, so nothing has to be set up twice.
05What does Search Deal do when no deal matches?
By default, it stops the Zap at that step and skips the steps that depended on it. You have two other choices. Switch on Successful if no search results are found? and the Zap carries on without a deal. Or tick Create X if it doesn't exist yet? and the search turns into a find-or-create that opens the deal for you, asking for the fields it needs. The same three settings apply to the other Moskit searches, except that Search User has no create option.
06What if the Moskit operation you want is not there?
Then the Zapier app does not offer it today. The Moskit page on Zapier shows the current list of triggers, actions and searches, so check it before you build. A few gaps are already clear: no action deletes a record, and no trigger fires on a new product or a new note. In that case, work around it with what exists, such as Archive Project, or look at what Make or n8n offer for Moskit.
07Zapier, Make or n8n for Moskit?
Choose on criteria, not on a ranking. On Zapier you get 60 ready operations for Moskit, with all 24 triggers instant, so the polling interval of a plan does not apply to them. Billing follows successful actions, so a Zap that searches, creates and notes grows in cost with volume. On Make or n8n, first check that a Moskit app exists with the event you need, then compare who will maintain the workflow and how each tool bills a run.
Same platform

Other docs you might need on this stack.

Browse all integrations