Ship a daily horoscope email, a natal chart on form submit, or an AI agent that calls live calculations as tools, on n8n in about 15 minutes, on Cloud or self-hosted.
The official RoxyAPI node is a verified n8n community node for astrology workflows and AI Agent tools on n8n Cloud and self-hosted n8n. One API key covers 18+ insight domains, including natal charts, horoscopes, Vedic kundli, compatibility, Human Design, tarot and numerology. The HTTP Request node reaches the same API with nothing to install, and the MCP Client Tool node gives an AI Agent a whole domain of tools at once.
The RoxyAPI AI astrology chatbot template is approved by n8n and published in its workflow template library. It runs multi-agent readings on web chat and Telegram, saves birth profiles, writes compatibility reports and sends daily forecasts, using Google Gemini, OpenAI or Anthropic.
Select Use for free on the n8n listing to start from the approved workflow. The template is free; you need a RoxyAPI key and an AI provider key. The MIT source and setup guide on GitHub cover customization, and the walkthrough video shows the full setup. For a single agent built from an empty canvas, watch the single-agent tutorial.
Run this in a terminal before you build anything. A 200 here means the key is good, so anything that fails next is wiring.
curl "https://roxyapi.com/api/v2/astrology/horoscope/aries/daily" \
-H "X-API-Key: $ROXY_API_KEY"No key yet? One plan covers every domain and checkout is instant: pricing.
Western Astrology, Operation Get Daily Horoscope, Sign Aries, and run it. The response is the same JSON as the curl above.Required inputs show as fields. Everything optional, including Language and Timezone, sits under Options → Add Option.
Never paste the key into a node field or an expression. The credential is encrypted by n8n and stays out of exported workflows; a field value travels with every workflow you export or share.
The instance owner or an admin installs the node once; everyone on the instance can then use it. On self-hosted n8n it also installs from Settings → Community Nodes → Install with @roxyapi/n8n-nodes-roxyapi.
No install, and the same API:
GET. URL https://roxyapi.com/api/v2/astrology/horoscope/aries/daily.X-API-Key, Value your key from your account. Rename the credential itself RoxyAPI key so it reads well in the dropdown.sign, date, overview, love, career, health, finance, advice, column, events, luckyNumber, luckyColor, compatibleSigns, activeTransits, moonSign, moonPhase, energyRating.Every later node picks that same credential from a dropdown. n8n encrypts credentials in its own database, so the value stays out of the node fields and out of an exported workflow, which carries only the credential name.
The API reference gives you a ready curl for any endpoint. Paste it into Import cURL on the HTTP Request Parameters tab and n8n fills in method, URL, and headers. One catch from the n8n docs: cURL import brings every value in as a string, so for a body with real numbers switch Specify Body to Using JSON afterwards. Then move the key out of the pasted header and onto the credential.
Every workflow below is one RoxyAPI node: pick the Resource and Operation, fill the required fields (map them from a form, a sheet or a webhook with expressions), and pass the JSON to any next node. The rows lead each domain with its most used calculation.
| Build this | Resource → Operation | Required fields |
|---|---|---|
| Daily horoscope email, post or push | Western Astrology → Get Daily Horoscope | Sign |
| Natal chart when a form is submitted | Western Astrology → Generate Natal Chart | Date, Time, Latitude, Longitude, Timezone |
| Love compatibility for a dating flow | Western Astrology → Calculate Synastry or Calculate Compatibility | Person1, Person2 |
| Vedic birth chart (kundli) | Vedic Astrology → Generate Birth Chart | Date, Time, Latitude, Longitude |
| Daily panchang for a city | Vedic Astrology → Get Detailed Panchang | Date, Latitude, Longitude |
| Kundli matching (gun milan) | Vedic Astrology → Calculate Gun Milan | Person1, Person2 |
| Upcoming transits for a user | Forecast → Forecast Transits | Birth Data |
| Human Design bodygraph | Human Design → Generate Bodygraph | Date, Time, Timezone |
| Chinese BaZi four pillars | Chinese Astrology → Generate Bazi Chart | Date, Time, Timezone |
| Feng shui Kua number | Feng Shui → Calculate Kua Number | Date, Gender |
| Life Path number | Numerology → Calculate Life Path | Year, Month, Day |
| Tarot reading bot | Tarot → Cast Three Card or Get Daily Card | none |
| Daily biorhythm | Biorhythm → Get Reading | Birth Date |
| I Ching reading | I-Ching → Cast Reading | none |
| Birthstones and crystals by sign | Crystal and Healing Stone → Get Crystals by Zodiac | Sign |
| Dream symbol lookup | Dream → Get Dream Symbol | ID |
| Angel number meaning | Angel Number → Get Angel Number | Number |
Charts need coordinates, so put Location and Timezone → Search Cities (field Query) in front of them and map latitude, longitude and timezone from its first city. Every Resource holds more operations than this table: open the node and they are listed by domain.
Charts, panchang, dasha, compatibility and synastry all take a birth moment.
Western Astrology, Operation Generate Natal Chart.{{ $json.birth_date }}, Time {{ $json.birth_time }}, Latitude {{ $json.latitude }}, Longitude {{ $json.longitude }}, Timezone {{ $json.timezone }}.The node sends Latitude and Longitude as numbers, and a Timezone that looks like a number (-5, 5.5) as a number too, so there is no JSON body to get wrong.
POST, URL https://roxyapi.com/api/v2/astrology/natal-chart.JSON. Specify Body Using JSON.{
"date": "{{ $json.birth_date }}",
"time": "{{ $json.birth_time }}",
"latitude": {{ $json.latitude }},
"longitude": {{ $json.longitude }},
"timezone": "{{ $json.timezone }}"
}date is YYYY-MM-DD and time is HH:MM:SS, both required, as are latitude, longitude and timezone. Optional houseSystem (placidus by default) and nodeType (true by default) sit alongside them.
curl -X POST "https://roxyapi.com/api/v2/astrology/natal-chart" \
-H "X-API-Key: $ROXY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"date": "1990-05-12",
"time": "14:30:00",
"latitude": 40.7128,
"longitude": -74.0060,
"timezone": "America/New_York"
}'If you move logic into a Code node or a custom node later, the typed client is one install:
import { createRoxy } from '@roxyapi/sdk';
const roxy = createRoxy(process.env.ROXY_API_KEY!);
const { data, error } = await roxy.astrology.generateNatalChart({
body: {
date: '1990-05-12',
time: '14:30:00',
latitude: 40.7128,
longitude: -74.0060,
timezone: 'America/New_York',
},
});
if (error) throw error;No visitor knows their birth latitude. Put a HTTP Request node on GET https://roxyapi.com/api/v2/location/search?q=berlin ahead of the chart node and read cities[0].latitude, cities[0].longitude and cities[0].timezone from it. The timezone it returns is an IANA name, which is what you want: the server resolves it to the correct offset for the birth date, so a summer birth and a winter birth are both right. A decimal offset like 5.5 is accepted but cannot know about daylight saving.
The response is plain JSON, so every field maps in any downstream node. planets is an array of objects with name, sign, degree, house, isRetrograde, dignity and more, so use a Split Out node to fan it out, or pick one inline:
{{ $json.planets.filter(p => p.name === 'Sun')[0].sign }}Three nodes, start to finish.
Western Astrology, Operation Get Daily Horoscope, Sign Aries. Under Options, add Timezone with the timezone of your readers, such as America/New_York, so the day turns over on their clock. With the HTTP Request node, the same call is https://roxyapi.com/api/v2/astrology/horoscope/aries/daily?timezone=America/New_York.Your daily horoscope, body {{ $json.column }}: the complete column for the day, 120 to 180 words, ready to send. For a push notification or SMS, send the 30 to 60 word {{ $json.overview }} instead.To cover all twelve signs, add a Loop Over Items node over the sign list and a short Wait between iterations rather than firing twelve calls at once.
Set the Language option on the node, or add ?lang= to any URL, for one of ten languages (en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant). The prose translates, and so does the sign a horoscope returns (?lang=hi returns सिंह for Leo), so branch an IF or Switch node on the sign you sent, never on the one that comes back.
This is where breadth on one key pays off: instead of wiring one endpoint per tool, you connect one server and the agent gets a whole domain.
Every domain has a Remote MCP server whose tools are generated from that domain spec, so you wire one node and the agent gets all of them.
https://roxyapi.com/mcp/astrology. Swap the last segment for any domain slug: vedic-astrology, tarot, numerology, human-design, location.HTTP Streamable. Our servers are Streamable HTTP, not SSE.Header Auth, and select the same RoxyAPI key credential from the HTTP call above. Bearer Auth with the key as the token works too.All to start. Once the agent works, switch to Selected and keep only what the assistant needs, because every exposed tool is a definition the model reads on every turn.Add one MCP Client Tool node per domain. Include the location server whenever a chart is in play so the agent can turn a city name into coordinates by itself.
Use a secret key here. Publishable pk_ keys are refused on the MCP endpoints.
For a few chosen operations, hand the agent the node itself.
Western Astrology and Generate Natal Chart.{{ $fromAI('sign', 'Zodiac sign in lowercase, for example scorpio') }}.The approved n8n AI astrology chatbot template takes this pattern further: specialist agents, each with its own RoxyAPI tools, behind one reader agent that resolves the city before any chart and passes every birth detail along. The video tutorial builds the single-agent version step by step.
For a single endpoint, skip MCP and hand the agent one HTTP Request node instead.
$fromAI, which takes a key, then an optional description, type and default:https://roxyapi.com/api/v2/astrology/horoscope/{{ $fromAI('sign', 'Zodiac sign, lowercase, for example aries', 'string', 'aries') }}/dailyRoxyAPI key credential.n8n does not cache HTTP responses. A horoscope is the same all day for a given sign, so store it: a Data table (built into n8n) or a Postgres table keyed by sign and date. Read the store, call RoxyAPI only on a miss, write the result back. One fetch per sign per day, however much traffic the workflow serves. The caching guide has the shelf life of every endpoint type.
That happens with Import cURL, which pastes the header value straight into the node. Move it to a Header auth credential and the export carries only a reference.
A 400 carries issues[] listing every field problem at once, so read that array rather than guessing one field at a time. All errors are { error, code, doc_url }. Retry 429 with code rate_limit_per_minute and 503 with code compute_saturated after the Retry-After seconds. Retry 500 with code internal_error with exponential backoff. A request that fails on our side with a 5xx does not count against your monthly allowance, so retrying it is free. A 429 with code rate_limit_exceeded means the monthly allowance is used up: retrying cannot help before the reset, and Retry-After gives the seconds to it. Fix the request for any other 4xx, because it will fail the same way until it changes. Every official SDK already retries these for you, twice and honouring Retry-After, so a call made through an SDK needs no second retry loop.
cURL import types every imported value as a string. Switch Specify Body to Using JSON and write latitude and longitude unquoted.
The container cannot reach roxyapi.com. Check outbound HTTPS on port 443, the firewall, and DNS inside the container.
Wrong method. The response names the methods that path accepts. Horoscopes and moon phases are GET; charts, spreads and readings are POST.
Read the response code: rate_limit_per_minute is the per-minute limit, so wait Retry-After seconds and retry; rate_limit_exceeded means the monthly allowance is used up. Put a Wait node inside the loop, cache daily content, or move up a plan. See authentication for the quota headers on every response.
Adding RoxyAPI from the agent Tool picker inserts it with its first operation. Open the tool and set Resource and Operation to the one the agent should call.
The expression editor closes {{ for you, so typing the closing }} as well leaves }} }} and the field never evaluates. Check that the expression ends with exactly one }}.
Install it first: select RoxyAPI in the nodes panel and press Install node. Only the instance owner or an admin can install it. On n8n Cloud, if search shows nothing, the owner turns verified community nodes on in the Cloud Admin Panel.
GET /astrology/horoscope/{sign}/daily, POST /astrology/natal-chart, POST /astrology/compatibility-score, POST /vedic-astrology/birth-chart, POST /vedic-astrology/panchang/detailed, POST /tarot/spreads/three-card, POST /numerology/life-path, POST /biorhythm/daily.Is there an official RoxyAPI node for n8n?
Yes. @roxyapi/n8n-nodes-roxyapi is the official RoxyAPI community node. It covers every endpoint across 18 domains as a Resource and an Operation, stores the key in one encrypted credential, and works as a normal workflow step or as a tool for the n8n AI Agent. n8n has verified it, so it installs from the nodes panel on n8n Cloud and on self-hosted n8n, and lists it on its RoxyAPI integration page.
Is there a ready n8n astrology AI agent or chatbot template?
Yes. The RoxyAPI AI astrology chatbot template is approved by n8n and available free in the official n8n workflow template library, with MIT source on GitHub. It provides specialist agents for Western and Vedic astrology, numerology, tarot, Human Design and BaZi, saved birth profiles, compatibility reports, web chat, Telegram and daily forecasts. Add a RoxyAPI key and a Google Gemini, OpenAI or Anthropic key to run readings from live calculations. The walkthrough video shows the setup.
How do I let the n8n AI Agent choose the zodiac sign?
Add the RoxyAPI node to the Tools input of the AI Agent, pick Western Astrology and Get Daily Horoscope, switch the Sign field to Expression, and write {{ $fromAI('sign', 'Zodiac sign in lowercase') }}. The model then fills the sign from the conversation, so asking about Scorpio calls the horoscope for Scorpio.
Can I use the RoxyAPI node on n8n Cloud?
Yes. RoxyAPI is a verified community node, so the instance owner or an admin installs it from the nodes panel: search for RoxyAPI, select it and press Install node. If search shows nothing, turn verified community nodes on in the Cloud Admin Panel.
Can n8n call an astrology API without any code?
Yes. The RoxyAPI node turns every endpoint across 18 domains into a form with a Resource, an Operation and input fields. Without installing anything, one HTTP Request node with a Header auth credential named X-API-Key reaches the same endpoints. Neither path needs a Code node.
How do I use RoxyAPI as a tool for an n8n AI Agent?
Two ways. For a whole domain at once, connect an MCP Client Tool node to the Tools input of the AI Agent, set the Endpoint to https://roxyapi.com/mcp/{domain}, set Server Transport to HTTP Streamable, and pick Header Auth with your X-API-Key credential. For a few chosen calculations, connect the RoxyAPI node itself as a tool, pick the Resource and Operation, and let the model fill the fields with Let the model define this parameter or $fromAI().
Where does n8n store my API key?
In a credential, which n8n encrypts in its database. The value stays out of the node fields and out of an exported workflow, which carries only the credential name. Importing a cURL command instead writes the key into the node itself, which is fine for a quick test and wrong for anything you export or share.
How do I turn a birth city into coordinates in n8n?
Call GET /location/search?q={city} in an HTTP Request node before the chart node and read latitude, longitude and timezone off the first city in the cities array. The timezone comes back as an IANA name, which handles daylight saving for the birth date automatically.
Does the free n8n tier work with RoxyAPI?
Yes. Self-hosted n8n is free and there is nothing paid on the RoxyAPI side of the wiring either: the RoxyAPI node is free to install, and the HTTP Request node, credentials, and the MCP Client Tool node are all standard. You need a RoxyAPI key, and one key covers all 18 domains.
Hi, I am Rosie, your guide to the RoxyAPI insight tools.
Ask me to read your birth chart, pull a card, or map your numbers, and I will interpret what it means for you. Unlike most AIs, I never make the numbers up: every reading runs on real, verified calculations. Curious about the API, pricing, or docs instead? Ask me that too.