OtherReal-timeUpdated June 2026

Pika integration

Pika AI video generation

Pika is the AI video lab whose Pika 1.x and Pika 2.x models compete in the open-API text-to-video space — known for stylised aesthetic options and image-driven character consistency. Tiny Command exposes two actions, no triggers: Generate Video (text-to-video or image-to-video with style options), Get Video (poll for async generation result). The connection uses a Pika API key. Pika's positioning is somewhat different from Runway/Luma/Kling — emphasises stylistic versatility (cinematic, anime, claymation styles via prompt hints). For workflows needing specific aesthetic styles that other models don't nail, Pika is worth testing. The standard async-with-polling pattern; pass a webhook URL for callback delivery on completion.

Connect Pika

No credit card required · Set up in under 2 minutes

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Pika can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs	Open action
Pika Generate Video	Text-to-video or image-to-video with Pika's stylised aesthetic options. For workflows needing specific styles other models don't nail (claymation, anime, watercolour).	4 inputs	View
Pika Get Video	Polls a Pika task; returns the video URL when complete. Configure callback for production push notification.	1 input	View

Recipes

Pre-built Pika workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Pika → Slack alerts

AI-triage every Pika event, ping the right channel only when it matters.

Pika → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Pika → Notion database

Turn Pika into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Pika once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Pika field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Pika integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Pika to Tiny Command?

Open the Tiny Command workflow builder, drop in a Pika node, and click Connect. Authorize Pika once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Pika triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Pika today. Use Tiny Command's universal Webhook or Schedule trigger to start Pika workflows, then run any Pika action you need.

What Pika actions can I run from a workflow?

2 Pika actions are available out of the box, covering other operations like "Pika Generate Video". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Pika integration real-time?

Pika actions execute synchronously inside your workflow. Tiny Command waits for Pika's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Pika with Tiny Command?

No. Every Pika trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Pika API endpoint directly.

How much does the Pika integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Pika integration itself has no per-app surcharge.