OpenRouter integration

What it does

The OpenRouter integration lets your agency invoke chat completions against any model OpenRouter routes to (OpenAI GPT, Anthropic Claude, Meta Llama, Mistral, Gemini, DeepSeek, and dozens more) from inside any workflow, billed against a single OpenRouter account. Connect a client's OpenRouter key once and your workflows can summarize incoming form submissions, classify support tickets, rewrite copy, generate structured JSON, or fan out the same prompt across multiple models for evaluation, all without juggling separate provider keys.

Connect an OpenRouter account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose OpenRouter and click Connect.
3. In a new tab, open the OpenRouter API keys page signed in as the client (or as your agency, if the client has delegated key management to you).
4. Click Create Key, give it a name that identifies the workspace, optionally set a credit limit, and copy the sk-or-v1-... value.
5. Paste the key into TaskJuice and save the connection.

To rotate or revoke the key later, return to the OpenRouter keys page and delete the entry; create a new key and update the TaskJuice connection.

Triggers

OpenRouter does not publish a public webhook surface, so the integration is action-only. Use a Schedule or another app's trigger to invoke OpenRouter actions inside a workflow.

Actions

• openrouter/create-chat-completion generates a chat completion against a chosen model slug (for example, openai/gpt-4o-mini, anthropic/claude-3.5-sonnet, meta-llama/llama-3.1-70b-instruct) with a list of messages and optional temperature, max tokens, top-p, and response-format controls.
• openrouter/list-models returns the catalog of routable models with context length and per-token pricing, useful for surfacing a model picker to end users or for branching on pricing tiers.
• openrouter/get-credits returns the remaining credit balance for the connected account, useful for budget alerts and proactive top-ups.

Known limitations

• The integration calls the OpenRouter REST API with the connected key. Per-key rate limits, credit caps, and model-access entitlements are governed by the client's OpenRouter account, not by TaskJuice. When OpenRouter returns a 429, TaskJuice surfaces it as a retryable rate-limit error and honors the recommended backoff.
• Streaming responses are not exposed. Each chat completion runs as a single request and resolves only after the full response is returned by OpenRouter.
• Provider routing rules (preferred provider, fallback order, data-collection opt-out) are configured on the OpenRouter account itself, not per request from TaskJuice. Set them in the OpenRouter dashboard before connecting the workspace.
• The integration is action-only. To react to events in real time, use a Schedule trigger, a polling trigger from another app, or an inbound webhook from a different source and call OpenRouter inside the workflow.