Connect Freshservice and Microsoft SharePoint to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Freshservice with Microsoft SharePoint - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "New Ticket" from Freshservice.
Add your action
An action happens after the trigger—such as "Copy File or Folder (Across Sites)" in Microsoft SharePoint.
You’re connected!
Zapier seamlessly connects Freshservice and Microsoft SharePoint, automating your workflow.
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 Ticket
Triggers when there is a new ticket is created in Freshservice.
Try ItTriggerInstant - Updated Ticket
Triggers when a Ticket is updated.
Try ItTriggerInstant - Ticket NoRequired
- NotesRequired
- PrivateRequired
ActionWrite- First NameRequired
- Last Name
- Job Title
- Primary EmailRequired
- Mobile Phone Number
- Work Phone Number
- Address
- Background Information
ActionWrite
- New User
Triggers when a new User is created.
Try ItTriggerInstant - Update User
Triggers when a user is updated.
Try ItTriggerInstant - SubjectRequired
- DescriptionRequired
- Ticket StatusRequired
- Type
- EmailRequired
- CC Emails
- Category
- Priority
- Urgency
- Impact
- Department
- Group
- Source
ActionWrite- Ticket
- Approval TypeRequired
- ApproverRequired
ActionWrite
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Frequently Asked Questions about Freshservice + Microsoft SharePoint integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Freshservice and Microsoft SharePoint
What is required to set up Freshservice with Microsoft SharePoint integration?
To set up Freshservice with Microsoft SharePoint integration, you will need access to both your Freshservice account and your SharePoint site. Make sure you have administrative permissions in both platforms. Then, connect them through the integration platform by authenticating at each step.
How can triggers be utilized in the Freshservice and SharePoint integration?
In our integration, triggers allow certain events in Freshservice, such as ticket creation or updates, to automatically perform actions in SharePoint like creating a list item or uploading a document.
Can we automate document handling between Freshservice and SharePoint?
Yes, you can automate document handling by setting up workflows where attaching a file in a Freshservice ticket automatically uploads it to a predefined document library in SharePoint.
What actions can be triggered from SharePoint back to Freshservice?
You can trigger actions such as ticket updates or new ticket creation in Freshservice when specific changes occur on your SharePoint lists or libraries, like when an item is added or modified.
How does authentication work between these integrations?
We use secure API connections to authenticate both accounts. You must authorize the integration before any data exchange occurs. Each platform will prompt for login details during initial setup.
Are there specific templates recommended for this integration?
We recommend using templates that match common workflows such as helpdesk ticket management synced with document revisions, which commonly align well with available triggers and actions.
Does this integration support conditional logic within workflows?
Yes, our integration supports conditional logic allowing you to define rules within workflows - for example, triggering different actions based on specific criteria like ticket priority levels or document metadata changes.