DesignVaultDocs

Automation recipes

Wire any generative-AI tool into DesignVault with no code. Each recipe ends in an HTTP POST to your generation inbox URL — the automation just reshapes the provider's output into the inbox body. Create the inbox URL first (Settings → API keys → Generation inbox).

The target: your inbox URL

Every recipe below POSTs JSON to the same endpoint:

POST https://www.designvault.net/api/v1/inbox/<your-url>
Content-Type: application/json

{ "image_url": "{{ the generated file URL }}", "title": "{{ prompt }}" }

For video, send { "video_url": "…", "poster_url": "…" } instead. The token in the URL is the credential — no auth header.

Zapier

  1. Trigger — your generator's “image/video ready” event (or Webhooks by Zapier → Catch Hook if you point the provider's callback at Zapier).
  2. Action — Webhooks by Zapier → POST.
  3. URL: your inbox URL. Payload type: JSON.
  4. Data: image_url = the trigger's output file URL, title = the prompt, tag_names = a comma value if you like.

Make (Integromat)

  1. Trigger module — your generator, or a Custom webhook the provider calls.
  2. Add an HTTP → Make a request module.
  3. Method POST, URL = your inbox URL, Body type Raw, content type JSON.
  4. Body: map the finished file URL into image_url (or video_url).

n8n

Use a Webhook node (provider callback) or your generator's node as the trigger, then an HTTP Request node:

Method:  POST
URL:     https://www.designvault.net/api/v1/inbox/<your-url>
Body:    JSON
{
  "image_url": "={{ $json.output[0] }}",
  "title":     "={{ $json.prompt }}"
}

Provider-specific notes

  • Replicate / fal.ai — set the prediction's webhook to your inbox URL directly if their payload contains a plain output URL; otherwise reshape via a Zapier/Make/n8n step (their bodies wrap the URL in their own JSON).
  • Google Vertex / Imagen & Veo — route the completion notification (Pub/Sub → Cloud Function, or an automation) to POST the resulting GCS/HTTPS URL.
  • Kling — video output: send video_url; add poster_url if the provider returns a thumbnail, else a placeholder is generated.

Why this shape

DesignVault deliberately does not integrate each provider one by one — their APIs change constantly. Instead every tool funnels into one ingestion endpoint. See the generation inbox for the full request contract, or the programmatic API for header-authed pushes.