When you need Box and HTTP Request talking to each other, here are the 75 n8n workflows in the catalog that already do it. Each is integration-tagged and privacy-stripped — copy the JSON and import.
Workflows that pair Box with HTTP Request
How it works Analyzes a reference product image using AI vision to extract brand elements, colors, and design Generates UGC-style prompts for image and video creation based on your specifications Call
This workflow ingests incoming lead data from a form submission webhook, enriches each lead with external data sources, applies a custom scoring algorithm, and automatically stores the enriched record
Automated n8n workflow: Receives videos via form, dubs/translates them to the selected languages, and—upon completion—uploads them to multiple social media channels and cloud drives, including Box, Dr
This workflow automatically schedules, packages, and uploads backups of your databases, files, or configuration exports to Box cloud storage, then sends a completion email via Mailgun. It is ideal for
Formtrigger Workflow_v122. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v88. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v79. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v87. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v41. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v70. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v65. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v10. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v881. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v316. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v670. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v378. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v116. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v226. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v566. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v969. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v498. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v826. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v389. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
Formtrigger Workflow_v217. Uses formTrigger, box, httpRequest. Event-driven trigger; 8 nodes.
See more Box workflows · HTTP Request workflows
FAQ
How do I trigger a HTTP Request action from Box?
Most workflows in this list use either a Box webhook trigger (real-time) or a polling trigger (every N minutes). From there, downstream HTTP Request nodes handle the action. Open any workflow's detail page to see the exact node graph.
Do I need both a Box and a HTTP Request account?
Yes — n8n connects to each integration via your own credentials. AutomationFlows strips credential IDs before publishing, so you'll add your own.
Are these Box → HTTP Request workflows free?
Yes — every workflow on AutomationFlows is free to browse and copy. Pro adds a multi-signal QualityScore on every workflow plus bulk JSON download.