Mattering Automations Fireworks AI integration
Connect Fireworks AI to Mattering Automations: chat and text completions on open-weight models, an Anthropic-format Messages endpoint, embeddings, document reranking, and dataset and fine-tuning management as workflow steps, authenticated with one Fireworks API key.
The Mattering Automations Fireworks AI integration puts Fireworks serverless inference on your automation canvas: run chat and text completions on open-weight models such as Kimi, Qwen, Llama, and DeepSeek inside a workflow step, call the Anthropic-format Messages endpoint, create embeddings, rerank documents by relevance, and read and manage the datasets and supervised fine-tuning jobs on your Fireworks account.
Setup is one API key from the Fireworks dashboard; the same key covers both Fireworks surfaces the connector uses, serverless inference and the account control plane. This guide covers creating the key, connecting it, a read-only verify path that also hands you the account ID the control-plane nodes need, and the full node reference, and it ends with the failure modes worth recognizing on sight.
Before you start
- A Fireworks AI account at app.fireworks.ai with permission to create an API key.
- A Mattering workspace with access to the Automations app.
- For the fine-tuning nodes, a training dataset already uploaded to Fireworks out of band, with firectl or the Fireworks SDK. The canvas has no file upload, so the integration picks the lifecycle up from an uploaded dataset onward.
- A budget awareness point: inference is billed per token and fine-tuning is billed by tokens processed, all on your Fireworks account. Starting a fine-tuning job from a workflow spends real money.
Create a Fireworks API key
Mattering authenticates to Fireworks with an API key sent as an Authorization bearer header. It is a single field: no organization id, no version header, no OAuth flow to complete.
Connect Fireworks AI to Mattering
Verify it works
Open any automation canvas and check the palette: a Fireworks AI section should list eight query nodes and eight action nodes. Drop Fireworks: List Accounts onto the canvas and run a test step. It takes no parameters and is read-only, so a successful response proves the key works and returns each account's ID, type, and state. Write down the account ID: the other control-plane nodes for models, datasets, and fine-tuning jobs take it as account_id.
Then run Fireworks: List Models. Its account_id defaults to fireworks, the shared public library, so it works with no configuration and returns the serverless catalog, with model IDs in the form accounts/fireworks/models/kimi-k2-instruct-0905. Set account_id to your own account ID instead to list the models you have uploaded or fine-tuned. This is the model discovery path: Fireworks has no models listing on its inference API, so the control plane is where the catalog lives.
To confirm inference itself, add Fireworks: Create Chat Completion, keep the default model, put one short message in the messages array, and set max_tokens low. A successful run returns the reply at choices[0].message.content along with token usage.
Node reference
16 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 8
Fireworks: Get Account
fireworks_get_account
Get one Fireworks account: display name, account type, state, and spend-notification settings.
Fireworks: Get Dataset
fireworks_get_dataset
Get one dataset: state, format, example count, and token estimate. Poll this after an out-of-band upload to wait for state READY before starting a fine-tuning job.
Fireworks: Get Fine-Tuning Job
fireworks_get_sft_job
Get one fine-tuning job: state, progress percent, estimated cost, and the outputModel to call once it reaches JOB_STATE_COMPLETED.
Fireworks: Get Model
fireworks_get_model
Get one model's details: state, kind, context length, and capability flags such as tool support, LoRA support, and serverless availability.
Fireworks: List Accounts
fireworks_list_accounts
List the Fireworks accounts the API key can access, with each account's ID, type, and state. Works with no parameters, so it doubles as the credential health check.
Fireworks: List Datasets
fireworks_list_datasets
List the datasets under a Fireworks account, with each dataset's state, format, and example count. Datasets are the training inputs for fine-tuning jobs.
Fireworks: List Fine-Tuning Jobs
fireworks_list_sft_jobs
List the supervised fine-tuning jobs on the account with their state, base model, output model, and estimated cost.
Fireworks: List Models
fireworks_list_models
List models under a Fireworks account. Use account ID 'fireworks' to browse the shared public model library, or your own account ID to list your uploaded and fine-tuned models.
Action nodes 8
Fireworks: Create Chat Completion
fireworks_create_chat_completion
Run a chat completion on Fireworks serverless inference. Send a messages array, get the assistant reply back at choices[0].message.content plus token usage. Supports tool calling, JSON-mode and JSON-schema structured output, vision models via image_url content parts, and reasoning models. Non-streaming.
Fireworks: Create Completion
fireworks_create_completion
Run a raw text completion: prompt in, continuation out at choices[0].text. Use this for base models or when you control the full prompt format yourself; use Create Chat Completion for instruct models. Non-streaming.
Fireworks: Create Embeddings
fireworks_create_embeddings
Turn text into embedding vectors for search, clustering, or similarity. Accepts a single string or a JSON array of up to 2048 strings; vectors come back at data[].embedding in input order.
Fireworks: Create Fine-Tuning Job
fireworks_create_sft_job
Start a supervised fine-tuning (LoRA) job over an uploaded dataset. Training is billed by tokens processed, so this spends real money. The job runs asynchronously: poll Get Fine-Tuning Job for state and the resulting outputModel.
Fireworks: Create Message (Anthropic Format)
fireworks_create_message
Run a Fireworks model through the Anthropic-compatible Messages endpoint: Messages-format request in, content blocks out at content[0].text. Useful when a flow or prompt library is already built around the Messages shape. Auth stays the Fireworks Bearer key. Non-streaming.
Fireworks: Delete Dataset
fireworks_delete_dataset
Permanently delete a dataset from the Fireworks account. This cannot be undone.
Fireworks: Delete Fine-Tuning Job
fireworks_delete_sft_job
Permanently delete a supervised fine-tuning job record. This cannot be undone.
Fireworks: Rerank Documents
fireworks_rerank_documents
Rerank a list of documents by relevance to a query using a Fireworks reranker model. Returns each document's index and relevance_score sorted best-first: the standard second stage after a keyword or vector search.
Using the integration
On the automation canvas
Fireworks nodes chain with everything else: pull a record, generate or classify with Fireworks: Create Chat Completion, then write the result into a task, a message, or a Database row. Template references resolve inside nested JSON, so an upstream node's output can drop straight into one entry of the messages array, a rerank documents list, or a tool definition, rather than templating the whole array as a single blob.
Three ways to run a model
Fireworks: Create Chat Completion is the standard messages in, choices out shape, with tool calling, JSON mode and JSON-schema structured output, vision input via image_url content parts, and reasoning models. Fireworks: Create Completion is prompt in, continuation out, for base models or when you control the full prompt format yourself. Fireworks: Create Message (Anthropic Format) runs Fireworks models through a Messages-compatible endpoint for prompts already built around that shape; auth stays the Fireworks key and the model field takes a Fireworks model ID. All three are non-streaming, so each node returns one complete response.
Embeddings and reranking
Fireworks: Create Embeddings accepts a single string or a JSON array of up to 2048 strings and returns vectors in input order at data[].embedding. Fireworks: Rerank Documents is the second stage: give it a query and a list of candidate documents and it returns each document's index and relevance_score sorted best-first, which is the standard follow-up to a keyword or vector search before handing results to a generation step.
The fine-tuning lifecycle
Upload the training dataset out of band, then poll Fireworks: Get Dataset until its state is READY. Fireworks: Create Fine-Tuning Job starts a supervised LoRA run over it, billed by tokens processed, and returns a job to poll with Fireworks: Get Fine-Tuning Job for state, progress, and estimated cost. When the job completes, pass its outputModel as the model on a chat completion. Fireworks: Delete Dataset and Fireworks: Delete Fine-Tuning Job are permanent, so point them only at resources you are done with.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can drive them, so an assistant can look up what a key can call, run inference, and check on a training job through the same 16 nodes the canvas uses.
Troubleshooting
Every node returns a 401
A control-plane node fails on account_id
A model id returns a not found or unavailable error
Replies come back shorter than max_tokens
Create Fine-Tuning Job is rejected
The Anthropic-format node errors on the model or max_tokens
There is no node for the endpoint you need
Related
The Fireworks AI MCP
What connecting Fireworks AI unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Fireworks AI is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.