Skip to content
Box logoiLoveAPI logo

Connect Box to iLoveAPI

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

Box triggers
3
Box actions
1
iLoveAPI triggers
11
iLoveAPI actions
22

Automation ideas

What you can build with Box and iLoveAPI

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

  • New File in Box creates Compress PDF in iLoveAPI

    Triggers when a file is uploaded

  • Task Completed in iLoveAPI creates Custom API Call in Box

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

  • New File in Box creates Merge PDF in iLoveAPI

    Triggers when a file is uploaded

  • Task Failed in iLoveAPI creates Custom API Call in Box

    Fires when a processing task fails. Optionally filter by tool.

  • New File in Box creates Split PDF in iLoveAPI

    Triggers when a file is uploaded

  • Signature Created in iLoveAPI creates Custom API Call in Box

    Fires when a new signature request is created.

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 Box 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.