Microsoft Outlook + Projul Integrations

Triggers at a specified time before an event in your calendar starts.

Triggers when an event is cancelled.

Triggers when an organizer cancels an event, for which the connected user is an attendee, on the selected calendar. In contrast to the instant Cancelled Calendar Event, this trigger also works with shared and delegated calendars.

Triggers when there is a new attachment.

Triggers when a new event is created in your calendar.

Triggers when a new contact is added to your account

Adds attendees to a calendar event.

Sets the categories applied to an email.

Adds a user to a distribution list or group. Only available in Microsoft 365 Business accounts that have organizational directories.

Create a duplicate of an email in a different folder.

Create an event in the calendar of your choice.

Creates a new contact.

Triggers when a client record changes in Projul — renamed, re-addressed, or given a new contact detail by a matched lead. Unarchiving a client fires this too.

Triggers when a client accepts an estimate. Acceptance happens in the Projul app or on the client's portal link and can never be done through an integration, so this is how an automation learns a job was won. Map "Estimate value" for the amount.

Triggers the moment a lead becomes won work — when its status crosses out of the lead stages. Use it to kick off onboarding, notify the crew, or update a CRM.

Triggers when a new client is added to Projul. A lead that matched an existing client does NOT fire this — Projul recognised them, so use Client Updated for that.

Triggers when a person creates an estimate in Projul. The hidden "ghost" estimates Projul keeps behind some projects for cost tracking do not fire this. Only real, user-created estimates do.

Triggers immediately when a lead is created in Projul. A lead is a project in a lead stage, so this fires on new projects whose status is one of the eight lead statuses.

Posts a message onto a project, task, client, or estimate in Projul. This is an internal note — it cannot send anything to a client.

Archives a client in Projul, taking them out of the active list. Reversible in the app. There is deliberately no Delete Client action — deleting a client also deletes their jobs, estimates and invoices, which is not something a Zap should do unattended.

Marks a Projul task complete, or reopens it. Running it twice is harmless. Careful with EstimateMeeting and EstimateToWrite tasks — completing one of those moves a lead along your sales pipeline.

Creates a client in Projul, or links to the one you already have. Projul matches on both names plus an email or phone, so running this on a list you have imported before will not produce duplicates.

Builds a draft estimate from one of your estimate templates, copying its sections, lines and pricing. The estimate is created as a draft — sending it and getting it approved stay human steps in Projul.

Creates a lead in Projul. A lead is a project in a lead stage, so this creates a project and links it to a client — matching an existing client rather than duplicating them.