No-Code Integrations

Use PolarGrid with n8n, Zapier, Make, and other automation tools

No-Code Integrations

PolarGrid’s OpenAI-compatible API works with any automation tool that supports HTTP requests. This guide shows how to connect from no-code platforms.

Authentication Setup

PolarGrid edge endpoints accept your pg_* API key directly — a single HTTP node is all you need.

Make Inference Calls

Configure an HTTP Request node:

Field	Value
Method	POST
URL	https://api.yto-01.edge.polargrid.ai/v1/chat/completions
Header	Authorization: Bearer pg_your_api_key
Header	Content-Type: application/json
Body	See below

{
  "model": "qwen-3.5-9b",
  "messages": [
    {"role": "user", "content": "Your prompt here"}
  ]
}

n8n

In n8n, use a single HTTP Request node:

• POST to https://api.yto-01.edge.polargrid.ai/v1/chat/completions
• Authorization: Bearer pg_your_api_key
• Content-Type: application/json
• Body: the chat completion JSON above

Store the API key in n8n’s credentials store rather than hardcoding it in the node.

Zapier / Make / Other Tools

Any tool with HTTP request support can call PolarGrid edge endpoints in a single step:

1. HTTP step: POST to the edge URL with Authorization: Bearer pg_*

The key differences per platform:

• Zapier: Use a “Webhooks by Zapier” action (Custom Request)
• Make (Integromat): Use an “HTTP — Make a request” module
• Pipedream: Use a Node.js or HTTP step

Available Endpoints

All standard PolarGrid endpoints work from no-code tools:

Endpoint	Use Case
POST /v1/chat/completions	Chat / text generation
POST /v1/audio/transcriptions	Speech-to-text (send audio file as form data)
POST /v1/audio/speech	Text-to-speech (returns audio bytes)
GET /v1/models	List available models

Choosing a Region

Pick the region closest to your automation platform’s servers:

Region	ID	Best For
Toronto	yto-01	US East, Eastern Canada
Vancouver	yvr-02	US West, Western Canada
Montreal	yul-01	Northeast US, Eastern Canada

Replace the region ID in the URL: https://api.{region-id}.edge.polargrid.ai