When new triggered webjob run in Azure Web Apps, sync it to QuickBooks Online.
When a WebJob finishes in Azure Web Apps, log automated process completion in QuickBooks Online.
See all Azure Web Apps + QuickBooks Online integrations or talk to a human
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Azure Web Apps Explore Azure Web Apps →
TriggersFires when a job, build or file conversion finishes in Azure Web Apps.
Fires when a job, build or API request fails in Azure Web Apps.
Calls an Azure Web Apps endpoint with data from an earlier step.
Creates a PDF, image or converted file with Azure Web Apps.
Checks or enriches a phone number, address or IP with Azure Web Apps.
QuickBooks Online Explore QuickBooks Online →
TriggersFires when a new invoice is created in QuickBooks Online.
Fires when a payment is recorded in QuickBooks Online.
Fires when an invoice in QuickBooks Online passes its due date unpaid.
Fires when a new expense is recorded in QuickBooks Online.
Creates a new invoice in QuickBooks Online.
Records a payment against an invoice in QuickBooks Online.
Creates a new expense entry in QuickBooks Online.
Syncs a customer's billing record in QuickBooks Online.
Enterprise-grade security
Common questions
Can Knit build “When new triggered webjob run in Azure Web Apps, sync it to QuickBooks Online.” between Azure Web Apps and QuickBooks Online?
Yes — describe it in the box above and Knit's Integrations Agent researches Azure Web Apps and QuickBooks Online's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.