Placid integration

What it does

The Placid integration turns a client's Placid templates into reusable workflow steps. Connect a client's Placid project once and your workflows can render images, multi-page PDFs, and multi-clip videos from structured data; poll a render until it finishes; list and pick templates at design time; and react in real time when Placid posts a render-completed notification to the configured webhook URL. Use it to fan out social cards, certificates, invoices, contracts, and short-form video from CRM records, form submissions, or scheduled triggers.

Connect a Placid account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Placid and click Connect.
3. In a new tab, open the Placid dashboard signed in as the client (or as your agency, if the client has delegated project access to you).
4. Click Projects, open the project whose templates you want to drive, and click API Tokens in the left menu.
5. Create a new API token and copy it. Placid tokens are project-scoped, so use a separate Placid project per client to keep credit usage attributable.
6. Paste the token into TaskJuice. It is injected as Authorization: Bearer <token> on every Placid API call.

To rotate or revoke credentials, return to API Tokens in the Placid project, revoke the existing token, generate a new one, and update the TaskJuice connection.

Triggers

• placid/render-completed fires when a render started by a Create Image, Create PDF, or Create Video action finishes. Placid POSTs the final resource (with id, status, the asset URL, and any passthrough metadata you supplied) once per render. Pass the trigger's inbound URL as webhook_success (and optionally webhook_error) on the create action, and set the X-TaskJuice-Inbound-Secret header on that URL to a shared secret you also paste into the TaskJuice trigger. TaskJuice verifies that header on every inbound POST before activating the workflow.

Actions

• placid/create-image generates an image from a Placid template with per-layer text and image overrides, optional output modifications (format, dimensions, filename), and optional S3 transfer.
• placid/create-pdf generates a multi-page PDF by stitching one or more templates, with per-page layer overrides and optional DPI and color-mode controls.
• placid/create-video generates a video by stitching one or more template clips, with optional audio track, fps, and dimension overrides.
• placid/get-image fetches the current status of a previously created image by id. Use to poll when you do not subscribe to the completion webhook.
• placid/list-templates pages through every template in the connected project, optionally filtered by collection, title substring, or tag, using page-number pagination.
• placid/delete-image removes a previously generated image by id.

Known limitations

• Placid bills in credits. One image up to 4000px is 1 credit; one PDF page up to 4000px is 2 credits; every 10 seconds of video is 10 credits. Per-account credit ceilings and plan-based feature entitlements are governed by the client's Placid plan, not by TaskJuice.
• Renders are asynchronous by default. The Create Image, Create PDF, and Create Video actions return status: queued immediately; the final URL appears only after the render finishes. Subscribe to placid/render-completed or poll Get Image to receive the finished asset.
• Placid does not sign render-completed webhook bodies. Treat the inbound URL plus the X-TaskJuice-Inbound-Secret header value as the secret and rotate them alongside the API token.
• The Create Image action's create_now flag renders synchronously and avoids the queue, but the request latency rises with template complexity and the request can time out before the asset is ready. Prefer the queued path with a webhook subscription for production traffic.
• API tokens are project-scoped. To drive templates from two Placid projects, create two TaskJuice connections, one per token.