Short answer: Drop the "Unsplash → Search Photos" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Search Query query | string | Required | Search Query. e.g. "mountain sunset" |
Results per Page per_page | number | Optional | Results per Page |
Orientation orientation | options | Optional | Orientation. Options: Any, Landscape, Portrait, Square |
{"query": "mountain sunset","per_page": "{{trigger.per_page}}","orientation": "{{trigger.orientation}}"}
{"total": 5000,"results": [{"id": "abc123","urls": {"small": "https://images.unsplash.com/...","regular": "https://images.unsplash.com/..."},"user": {"name": "Photographer"},"likes": 150,"description": "Mountain at sunset"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.