Create integrations between Azure Web Apps and Moskit to automate any workflow
How Zapier works
Zapier lets you build automated workflows between two or more apps—no code necessary. These workflows are called Zaps, and this is how they work.
A trigger is where automation begins
Now it's time for action
And that's it! You've just created a Zap.
Connect your tools and unlock the power of automation
With Zapier's 6,000 integrations, you can unify your tools within a connected system to improve your team's efficiency and deepen their impact.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
New Web App Deployment
Triggers whenever a Git, Mercurial or Dropbox deployment to a Windows Azure Web Site completes (whether it succeeds or fails). Useful for Continuous Deployment workflows.
Try ItActivity Completion Attemp
Triggers when activity is try.
Try ItActivity Completed
Triggers when a new activity is done.
Try ItActivity Updated
Triggers when a new activity is updated.
Try It
New Triggered WebJob Run
Triggers whenever your scheduled or on-demand WebJob completes a run.
Try ItNew Activity Created
Triggers when a new activity is created.
Try ItActivity Responsible Changed
Triggers when activity responsible is changed.
Try ItNew Company Created
Triggers when a new company is created.
Try It