Microsoft Outlook automations — Tickets & Requests

Ready-made scenarios where Microsoft Outlook works for you (tickets & requests): pick one — a copy appears in your account and runs on its own.

80 scenarios

Updated deals in Pipedrive — Contacts in Microsoft Outlook
New emails in Microsoft Outlook — Conversations in Help Scout
Updated tickets in hubspot — Updating events in Microsoft Outlook
Updated form responses in Onfleet — Updating contacts in Microsoft Outlook
New tickets in Zendesk — Folders in Microsoft Outlook
Updated tickets in Salesforce — Folders in Microsoft Outlook
Updated tickets in Zendesk — Contacts in Microsoft Outlook
New tickets in Zendesk — Emails in Microsoft Outlook
New tickets in Zendesk — Deleting emails in Microsoft Outlook
New tickets in HubSpot — Files in Microsoft Outlook
Updated tickets in hubspot — Sending emails in Microsoft Outlook
New conversations in Help Scout — Drafts in Microsoft Outlook
Complaint: campaigns in mailerLite — Contacts in Microsoft Outlook
New tickets in Zendesk — Events in Microsoft Outlook
Found: groups in zendesk — Contacts in Microsoft Outlook
New tickets in Salesforce — Drafts in Microsoft Outlook
New tickets in Zendesk — Contacts in Microsoft Outlook
Updated tickets in Zendesk — Updating contacts in Microsoft Outlook
New users in Zendesk — Running apis in Microsoft Outlook
New emails in Microsoft Outlook — Updating tickets in HubSpot
New conversations in microsoftTeams — Running apis in Microsoft Outlook
New views in zendesk — Events in Microsoft Outlook
Found: groups in zendesk — Sending emails in Microsoft Outlook
Updated tickets in hubspot — Events in Microsoft Outlook
New emails in Microsoft Outlook — Tickets in Freshdesk
Updated events in Microsoft Outlook — Updating tickets in Zendesk
Updated conversations in helpScout — Drafts in Microsoft Outlook
Starting soon: events in microsoftOutlook — Tickets in Freshdesk
New tickets in HubSpot — Calendars in Microsoft Outlook
Starting soon: events in microsoftOutlook — Deleting users in Zendesk
Updated tickets in freshdesk — Running apis in Microsoft Outlook
Found: files in Microsoft Outlook — Deleting users in Zendesk
New folders in Microsoft Outlook — Tickets in Freshdesk
Deleted contacts in Microsoft Outlook — Updating companies in Amo Crm
New calendars in Microsoft Outlook — Tickets in HubSpot
New folders in Microsoft Outlook — Updating tickets in Zendesk
Updated contacts in Freshdesk — Tickets in Freshdesk
New tickets in Freshdesk — Sending emails in Microsoft Outlook
Found: files in Microsoft Outlook — Customers in Shopify
New contacts in Microsoft Outlook — Conversations in Gmail
Updated tickets in freshdesk — Events in Microsoft Outlook
Updated contacts in freshdesk — Updating emails in Microsoft Outlook
Deleted contacts in Microsoft Outlook — Updating tickets in Zendesk
Updated tickets in freshdesk — Sending emails in Microsoft Outlook
New tickets in freshdesk — Running apis in Microsoft Outlook
New emails in Microsoft Outlook — Tickets in HubSpot
New tickets in Zendesk — Events in Microsoft Outlook — variant 2
New contacts in Microsoft Outlook — Updating users in Zendesk
New form responses in Formstack — Updating users in Zendesk
Updated cards in mondayCom — Running apis in Microsoft Outlook
Zendesk users as records in Microsoft Outlook
Urgent messages from Telegram — into Telegram and Zendesk
Support emails — into tickets automatically
Support emails, summarized into your messenger
Website enquiry intake — a ticket log and an instant reply
A form request into a tracker issue
Customer emails become support tickets with a spreadsheet log
Turn support emails into tracker tickets automatically
Support emails become tracker issues automatically
Support emails become tickets with a priority attached
All customer inquiries in one place — from email and web forms
Tickets from email and forms — into one stream
Stuck tickets, followed up automatically
Upsell signals from support tickets
Data-privacy complaint handling: register, reply, notify
Smart support triage with amoCrm
Support performance report with SLA — by email
Support emails become tickets with an ID and an owner
A summary of support tickets — topics and customer mood
Support ticket replies drawn from your own FAQ list
Support emails into Jira tickets with an AI reply
Tell customers their bug is fixed — the moment the issue closes
Payment issue handling: a reply to the customer, an escalation to the team
Support tickets turned into a prioritized engineering backlog
A full new-client welcome after the form
Website enquiries: contact, ticket and reply with no manual entry
Maintenance tickets: contractor matched by area, dispatched, duplicates caught
AI support in your messenger, built on your own materials
Signups, support and billing — run by one assistant
AI support across every channel, grounded in your docs