Skip to main content
Foundry is a first-class action inside Zapier. Wire it into any Zap to run a prompt, route across models, generate an image, or kick off Deep Research — triggered by anything Zapier can listen to.
Screenshot coming. Zapier action picker with IronLabs / Foundry.

​
What you can build

  • Inbound email → routed reply. When a customer email lands, run a Foundry prompt that drafts a reply and posts it to Slack for review.
  • New Notion row → summary. Auto-summarize a new Notion entry and append the summary as a comment.
  • Cron → daily brief. Pull yesterday’s metrics from your data warehouse, ask Foundry for a one-paragraph summary, post to Slack.
  • Webhook → image. A form submission triggers an image generation in Foundry Image Mode and emails the result.

​
Setup

  1. In Zapier, search for IronLabs (or Foundry) and pick the action you want — Run Prompt, Generate Image, Deep Research.
  2. Connect your IronLabs account once. You’ll need your API key from app.ironlabs.ai.
  3. Map your trigger payload into the action’s fields (prompt, model preferences, etc.).
  4. Test and turn on.

​
Tips

  • Keep prompts templated. Use Zapier’s field-merge to inject trigger data without rewriting the prompt every time.
  • Pick a tradeoff. For Zaps, latency or cost usually beats quality — most Zap outputs don’t need the heaviest model.
  • Log the run. Pipe the response into a Notion or Airtable row so you have a paper trail.

​
Limits

  • Zapier rate limits apply (Free vs Pro plan).
  • Long-running operations (Deep Research, big video generations) can exceed Zapier’s per-action timeout — split into multiple steps or use Foundry’s webhook callback pattern.

Connectors overview

Other ways to wire up tools.

Scheduled tasks

Cron without leaving Foundry.