AstroLogics API

Use the API from n8n

n8n is a tool for building automations from connected steps. There is no AstroLogics node for it, and you do not need one: its HTTP Request node can call every operation in the API reference.

We imported and ran both workflows below in n8n 2.45.7, against a stand-in server that returned our documented example responses. They have not yet run against a live key. If yours behaves differently, tell us at developers@astrologics.in.

1. Save your key as a credential

Keep your key in an n8n credential, not in a node, so it is never included when you share or export a workflow.

  1. Create a key on the API keys page. A test key (al_test_) is free to try with and is never charged.
  2. In n8n, open Credentials and create a Header Auth credential.
  3. Set Name to Authorization, and Value to Bearer followed by a space and your key.
  4. Save it as AstroLogics API key.

2. Import a workflow

Download a file, then in a new n8n workflow open the menu at the top right and choose Import from File.

Workflow What it does Credits for each run
Daily panchang Each morning at 6:00, gets the day's panchang and writes one line of text 1
Daily horoscope on WhatsApp Each morning at 7:00, gets one sign's reading and sends it through AiSensy. See the WhatsApp guide first 1

After importing:

  1. Open each HTTP Request node and choose your credential. An imported workflow does not carry one.
  2. Change the values in the Settings node.
  3. Choose Execute workflow to run it once by hand, and check each step's output.
  4. Turn the workflow on, so that the schedule runs it. Both start switched off.

The daily panchang ends with a line of text in a field named message, like this:

2026-10-02: Saptami, Mrigashira. Rahu kaal 10:41 to 12:10.

Connect any n8n step after it to send that line on, such as email, Telegram or Slack.

3. Call any other operation

Add an HTTP Request node and fill it in from the operation's page in the API reference:

Field Value
Method The operation's method
URL https://api.astrologics.in, then the operation's path
Authentication Generic Credential Type, then Header Auth, then AstroLogics API key
Query parameters Those listed for the operation
Body For POST operations, JSON as shown in the operation's example

The response is always data, meta and warnings, so later steps read values such as {{ $json.data.tithi.label }}.

Birth details and your n8n history

We never store request bodies. n8n is separate: it can save the input and output of every run, and that would include any birth details your workflow handles. Both workflows here are set not to save successful runs, but a failed run is still saved. If you add a step that handles a client's birth details, send them in a POST body, and check Settings for the workflow, including what it saves when a run fails. See caching and data retention.

When a call fails

The HTTP Request node stops the workflow on an error response. The body holds the code and the message, listed in errors. For a run on a schedule, set an error workflow in the workflow's settings, so that you hear about it.

A call that returns 429 has reached your rate limit. In the node's settings, turn on Retry On Fail, with a wait between tries.