> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/nodes/public-ai-llm-models/byteplus-cloud.md).

# BytePlus Cloud

The **BytePlus Cloud** node lets you use BytePlus inside a Diaflow workflow with your own API key. It is a good fit when your team wants one provider that can support different content types, such as text, images, or video.

<figure><img src="/files/n7WVFIRkWCRnXdDRXOen" alt=""><figcaption></figcaption></figure>

You can use this node for tasks such as writing content, summarizing information, generating visuals, or creating media outputs for campaigns, presentations, and business operations.

{% hint style="info" %}
Diaflow runs the workflow. BytePlus charges usage to your own BytePlus account.
{% endhint %}

## What this node does

The node takes your instruction, sends it to the selected BytePlus model, and returns the result to the next step in your workflow. Depending on the model you choose, the result can be text, an image result, or a video result.

You can also pass content from earlier steps into this node. For example, you can send a product brief, campaign notes, customer request, or uploaded file and ask BytePlus to generate a business-ready output.

## When to use it

Use **BytePlus Cloud** when you want Diaflow to work with your own BytePlus setup and need flexibility across more than one content type.

Common use cases include:

* Draft marketing copy, summaries, and business content.
* Generate creative images from a short brief.
* Create media outputs for product demos, campaigns, or visual concepts.

## Before you start

Make sure you have:

* An active BytePlus account.
* A valid BytePlus API key.
* Permission to use the model you want.

## How to set it up

Set up the node in this order:

1. In **Credentials**, choose your saved BytePlus key.
2. In **Model**, choose the BytePlus model that fits your task.
3. In **Prompt**, describe what you want the model to do.
4. Run the node and review the result.

<figure><img src="/files/BcYlTsO3ayIrlmdcOIfz" alt="" width="375"><figcaption></figcaption></figure>

If you want the model to work from earlier workflow data, insert that data into the prompt with `@`.

## What each field means

### Credentials

This is where you select the BytePlus API key your team wants to use. If the correct key is not listed, add it first, then refresh the list if needed.

### Model

This is where you choose the BytePlus model. The list depends on the key and account you connected.

For most business users, the choice is simple:

* Choose a text model for writing, summarizing, and question answering.
* Choose an image model when you want visuals from a written brief.
* Choose a video-capable model when you need richer media output.

If you are unsure, start with the content type you need first, then compare results using a real business example.

### Prompt

This is the instruction you give the model. Write it in plain language and focus on the business result you want.

A strong prompt usually includes:

* the task
* the context
* the expected format or style

For example:

```
Write a short product launch announcement for business customers.
Keep the tone professional and clear.
Return 3 headline options and 1 short body paragraph.
```

If your workflow already has data from previous steps, insert it into the prompt with `@` so the model uses that content directly.

### Formatted

Use this field when you want the result in a more predictable structure. This is helpful when another node needs the output in a specific format, or when you want more consistent results across repeated runs.

## What you get back

The node returns the model’s result to the next step in your workflow. The output type depends on the model you selected. In many cases, the result is text. Some models can return image or video outputs.

## Tips for business users

* Start with one clear task in each prompt.
* Match the model to the content type you need.
* Ask for a specific output format, such as bullets, short copy, image concept, or structured text.
* Test with a real business brief before using the node in a live workflow.

### Next steps

* Compare other providers in [Public AI/LLM Models](/workflow-builder/nodes/public-ai-llm-models.md).
* Learn the workflow basics in [Overview](/workflow-builder/overview.md).
* Browse more nodes in [Component List](/workflow-builder/component-list.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.diaflow.io/workflow-builder/nodes/public-ai-llm-models/byteplus-cloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
