Skip to content
Microsoft SharePoint logoiLoveAPI logo

Connect Microsoft SharePoint to iLoveAPI

Move data between Microsoft SharePoint and iLoveAPI the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Microsoft SharePoint triggers
8
Microsoft SharePoint actions
16
iLoveAPI triggers
11
iLoveAPI actions
22

Automation ideas

What you can build with Microsoft SharePoint and iLoveAPI

A few flows teams run between Microsoft SharePoint and iLoveAPI. Use one as a starting point, or build your own from scratch.

  • New File in Folder in Microsoft SharePoint creates Compress PDF in iLoveAPI

    Fires when a new file is created or added in a specific folder.

  • Task Completed in iLoveAPI creates Create Folder in Microsoft SharePoint

    Fires when a processing task finishes successfully. Optionally filter by tool.

  • New File in Folder in Microsoft SharePoint creates Merge PDF in iLoveAPI

    Fires when a new file is created or added in a specific folder.

  • Task Completed in iLoveAPI creates Create List in Microsoft SharePoint

    Fires when a processing task finishes successfully. Optionally filter by tool.

  • New File in Folder in Microsoft SharePoint creates Split PDF in iLoveAPI

    Fires when a new file is created or added in a specific folder.

  • Task Completed in iLoveAPI creates Create List Item in Microsoft SharePoint

    Fires when a processing task finishes successfully. Optionally filter by tool.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Microsoft SharePoint and acts in iLoveAPI, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.