How to integrate my algorithm API into Dify?

[AdaChamberss]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

I have already developed my own algorithm and packaged it as an API that can be requested via a URL. How can I integrate it into a Dify workflow? Is it possible to set up a node to request this API?

[dosubot[bot]]

You can integrate your algorithm API into a Dify workflow using either an HTTP Request Node or a Code Node:

1. HTTP Request Node:
Add an HTTP Request node to your workflow. Configure the method (GET, POST, etc.), the full URL of your API (make sure to use your machine’s LAN IP or host.docker.internal if running in Docker, not localhost), headers, body, and any required authorization. You can use variables like {{input}} in the URL, headers, or body, but these must be defined as inputs in your workflow’s Start Node to be resolved correctly. The node supports dynamic templating, various body types (JSON, form-data, etc.), and API key/bearer/custom header authorization. The response (status, body, headers, files) is available for downstream nodes.
See implementation details

2. Code Node:
For more advanced scenarios, add a Code Node (Python or JavaScript) to your workflow. Here you can write custom code to call your API using libraries like httpx in Python. This is useful if you need custom logic, special error handling, or to process the API response before passing it along.
Example (Python):

import httpx

def main(input_value: str) -> dict:
    response = httpx.post("http://your-api-url/endpoint", json={"input": input_value})
    response.raise_for_status()
    return {"result": response.json()}

See code node details

Important tips:

• Always use the full URL scheme (http:// or https://) and verify your API is reachable from inside the Dify environment.
• Avoid curly braces {} in the URL path—replace them with actual values.
• If you want to pass dynamic parameters, define them as inputs in the Start Node and reference them as {{variable}} in your HTTP node or code.
• There is a known issue where variables like {{name}} may not resolve if the workflow is used as a tool in an agent context (details).
• If your API requires special message formats, ensure your node or code matches those requirements.

Workflow example diagram:

graph LR
    A["Start Node (inputs)"] --> B["HTTP Request Node or Code Node"]
    B --> C["Next Workflow Step"]

Loading

If you have advanced needs (like plugin development, file handling, or agent integration), let me know your scenario!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}