corezoid-gitcall

# Corezoid Git Call A Git Call node runs your code (9 built-in languages, or a custom Docker image) in an isolated container as one step of a process. Each task is delivered to a `handle` function over JSON-RPC 2.0; the value you return becomes the payload of the next node. Reach for Git Call only when the standard nodes cannot do the job. It is heavier than a Code (`api_code`) node — it needs a container build and a warm-up. ## 1. When to use it Use Git Call when you need something the platform's built-in nodes lack: - Parse files (download a URL and read a 1C `.1CD`, XML, PDF, QR, image, …). - Use external libraries (crypto, moment, pandas, okhttp, …). - Heavy/custom logic (matrices, cryptography, bespoke formats). - Build an email body with attachments, generate documents, etc. | Aspect | Code node (`api_code`) | Git Call | |---------------|------------------------|---------------------| | Speed | faster | slower | | Warm-up | none | required | | Complexity | simple | higher | | Resources | efficient | heavier (container) | | External deps | no | yes | | Languages | JS (+ limited) | 9 languages + Docker | Rule of thumb: simple and fast with no external deps → Code node. Files, libraries, or custom runtimes → Git Call. ## 2. Supported languages and runtimes | Language | Version ...