Skip to content
Google Drive logoiLoveAPI logo

Connect Google Drive to iLoveAPI

Move data between Google Drive 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.

Google Drive triggers
3
Google Drive actions
17
iLoveAPI triggers
11
iLoveAPI actions
22

Automation ideas

What you can build with Google Drive and iLoveAPI

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

  • New File in Google Drive creates Compress PDF in iLoveAPI

    Trigger when a new file is uploaded.

  • Task Completed in iLoveAPI creates Create new folder in Google Drive

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

  • New File in Google Drive creates Merge PDF in iLoveAPI

    Trigger when a new file is uploaded.

  • Task Completed in iLoveAPI creates Create new file in Google Drive

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

  • New File in Google Drive creates Split PDF in iLoveAPI

    Trigger when a new file is uploaded.

  • Task Completed in iLoveAPI creates Upload file in Google Drive

    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 Google Drive 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.