Automate Daily Horoscope Delivery with Make and an API

About the author: Brett Calloway is a Developer Advocate and AI Integration Specialist with 12 years of experience building APIs and developer tooling, including three years focused on AI-native infrastructure for spiritual and wellness applications. He has led developer relations at two Series B SaaS companies and spoken at PyCon and JSConf on building context-rich AI agents using Model Context Protocol. His writing covers API integration patterns, AI agent architecture, and rapid prototyping with astrology, tarot, and numerology data.

Daily horoscopes are one of the highest engagement content types in wellness and lifestyle apps. Newsletters with zodiac content see 2x to 3x the open rates of standard marketing emails. But manually fetching and formatting horoscope data every morning is tedious and error-prone. Most teams either skip it or hardcode generic text that never changes.

What if your daily horoscope arrived automatically every morning, already formatted, with real planetary transit data behind it? With Make and a horoscope API, you can build this in under 30 minutes. This guide walks you through creating a Make scenario that fetches a transit-based daily horoscope, parses the JSON response, and delivers it to Email, Slack, or Telegram on a schedule. No code required.

What you will build

This tutorial creates a Make scenario with four modules chained together. A Schedule trigger fires once per day at a time you choose. An HTTP module sends a GET request to the Western Astrology API daily horoscope endpoint and returns structured JSON with the daily overview, love forecast, career outlook, health guidance, finance tips, lucky number, lucky color, and compatible signs. A JSON parse module extracts each field into mappable variables. A final delivery module sends the formatted horoscope to your chosen channel: email, Slack, Telegram, Discord, Google Sheets, Notion, or any of the 1,800+ apps in the Make library. The entire flow runs unattended. You set it up once, activate it, and your audience receives fresh horoscope content every day.

Ready to build this? RoxyAPI Western Astrology API gives you daily, weekly, and monthly horoscopes for all 12 zodiac signs in a single GET request. See pricing.

Prerequisites

You need two things before you start. First, a free Make account at make.com. The free tier includes 1,000 operations per month, which is more than enough for daily horoscope delivery. You do not need a paid Make plan for this workflow. Second, you need a RoxyAPI API key. Visit the pricing page and choose any plan. Your API key is delivered instantly by email, and it works across all 120+ endpoints with a single subscription. No separate activation is needed for the astrology endpoints. Copy your API key and keep it ready. You will paste it into the HTTP module header configuration in the next step. One important note: each Make operation that calls the API counts as one request against your RoxyAPI plan. A single daily call for one sign uses roughly 30 requests per month.

Step 1: Create a new scenario with Schedule trigger

Log in to Make and click "Create a new scenario" in the top right corner. You land on a blank canvas with a single empty circle. Click the circle and search for "Schedule" in the module picker. Select the Schedule trigger module (the clock icon). This is the module that tells Make when to run your scenario. Set the interval to "Days" and enter 1 for the repeat cycle. Under "Time," choose when you want the horoscope delivered. For a morning newsletter, set it to 06:00 or 07:00 in your local timezone. Make converts this to UTC internally, so your scenario fires at the same local time regardless of daylight saving changes. Click OK to save the trigger. You now have a scenario that activates once per day at your chosen time.

Step 2: Add the HTTP module for the API request

Click the plus icon to the right of the Schedule trigger to add a new module. Search for "HTTP" and select "Make a request" from the HTTP app (not the webhook module). This is where you configure the API call. Set the following fields:

URL:

https://roxyapi.com/api/v2/astrology/horoscope/aries/daily

Method: GET

Headers: Click "Add a header" and enter:

• Name: X-API-Key
• Value: Your RoxyAPI API key

Leave the body empty. Daily horoscope is a GET endpoint with no request body. The zodiac sign is part of the URL path. Replace aries with any of the 12 signs: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, or pisces. Set "Parse response" to Yes. This tells Make to automatically convert the JSON response into mappable fields. Click OK, then click "Run once" in the bottom left to test. You should see a green checkmark with the full response data.

Step 3: Parse the JSON response

After the HTTP module runs successfully, the parsed response contains these fields you can map to downstream modules:

{
  "sign": "Aries",
  "date": "2026-04-01",
  "overview": "Mars trine Jupiter brings bold energy to new ventures today. Trust your instincts on financial decisions and creative projects.",
  "love": "Venus in your fifth house sparks playful connections. Existing relationships benefit from spontaneous gestures.",
  "career": "Saturn sextile your Sun rewards disciplined effort. A proposal or presentation lands well with decision makers.",
  "health": "High energy from Mars transit supports intense workouts. Stay hydrated and avoid skipping meals.",
  "finance": "Jupiter aspect favors calculated risks. Review investment opportunities but avoid impulsive spending.",
  "advice": "Channel the Mars-Jupiter trine into action. Start the project you have been planning.",
  "luckyNumber": 7,
  "luckyColor": "Gold",
  "compatibleSigns": ["Leo", "Sagittarius", "Gemini"]
}

Every field is available as a drag-and-drop variable in subsequent modules. The overview field contains the general daily forecast. The love, career, health, and finance fields provide category-specific guidance. The luckyNumber, luckyColor, and compatibleSigns fields add engagement hooks that readers love. If you enabled "Parse response" in the previous step, these fields are already extracted. If you need explicit parsing, add a JSON > Parse JSON module between the HTTP module and your delivery module, then map the HTTP response body into it.

Step 4: Send via Email, Slack, or Telegram

Click the plus icon after the HTTP (or JSON parse) module and choose your delivery channel. Here are configurations for three popular options.

Email (Gmail or SMTP): Search for "Email" or "Gmail" in the module picker. Select "Send an email" and connect your account. In the Subject field, type something like: Your Aries Horoscope for {{date}}. In the HTML body, map the response fields:

<h2>Daily Horoscope: {{sign}}</h2>
<p>{{overview}}</p>
<h3>Love</h3><p>{{love}}</p>
<h3>Career</h3><p>{{career}}</p>
<h3>Health</h3><p>{{health}}</p>
<h3>Finance</h3><p>{{finance}}</p>
<p><strong>Lucky Number:</strong> {{luckyNumber}}</p>
<p><strong>Lucky Color:</strong> {{luckyColor}}</p>

Slack: Search for "Slack" and select "Send a Message." Choose the target channel and format the message using Slack markdown with the mapped fields.

Telegram: Search for "Telegram Bot" and select "Send a Message." Enter your chat ID and format the horoscope using the mapped response fields with Telegram markdown.

Step 5: Activate the scenario

Before activating, run the complete scenario once more using the "Run once" button. Verify that each module shows a green checkmark and your test message arrives in the target channel. Check the output of the HTTP module to confirm all response fields are populated. Once satisfied, click the toggle switch in the bottom left corner to change the scenario status from OFF to ON. The label changes to "Active" and turns green. Your scenario now runs automatically at the scheduled time every day. Make sends you a notification email if any module fails, so you will know immediately if something goes wrong.

Extend: Loop through all 12 zodiac signs

The single-sign setup is great for personal use. For a newsletter or app that serves all 12 signs, you have two options.

Option A: Use the all-signs endpoint. RoxyAPI provides a batch endpoint that returns daily horoscopes for all 12 zodiac signs in a single request:

GET https://roxyapi.com/api/v2/astrology/horoscope/daily

This returns a JSON object with a date field and a horoscopes array containing all 12 forecasts. One API call, one request on your plan, all 12 signs. Use a Make Iterator module to loop through the horoscopes array and process each sign individually. This is the most efficient approach for multi-sign delivery.

Option B: Use a Make Repeater module. Add a Repeater module after the Schedule trigger, set it to repeat 12 times, and build an array of sign names. Map the current sign into the HTTP module URL. This makes 12 separate API calls per day (12 requests on your plan). Option A is better for most use cases because it is faster and uses fewer API requests.

For the full endpoint reference, see the Western Astrology API documentation.

Common pitfalls and troubleshooting

401 error (api_key_required or invalid_api_key): The most common issue is a missing or malformed X-API-Key header. Double check that the header name is exactly X-API-Key (with capital X, A, and K). Verify there are no extra spaces before or after the key value. Make sure you are using the full API key string, not just the prefix.

Empty response body: If "Parse response" is set to No, the HTTP module returns raw text instead of structured data. Toggle it to Yes and run the module again. You should see individual fields appear in the output panel.

Rate limit errors (429): If you hit a 429 response, your monthly request quota is exhausted. Check your current usage by calling GET /api/v2/usage with your API key. Consider upgrading your plan at roxyapi.com/pricing if you need more requests.

Timezone mismatch on schedule: Make runs scheduled scenarios in UTC by default. If your horoscope arrives at the wrong local time, adjust the Schedule trigger time to account for your UTC offset. The API always returns the current day horoscope based on UTC date.

Scenario turns off after errors: Make automatically deactivates scenarios after consecutive failures. Check the scenario log for the specific error, fix the issue, and reactivate. A common cause is an expired or rotated API key.

Frequently Asked Questions

Q: How many API requests does this automation use per month? A: A single-sign daily scenario uses roughly 30 requests per month (one per day). Using the all-signs batch endpoint (/horoscope/daily) for all 12 signs still uses only 30 requests per month because it returns every sign in one call. The Starter plan at 5,000 requests per month provides more than enough capacity.

Q: Does the daily horoscope change every day? A: Yes. The daily horoscope endpoint generates forecasts based on real planetary transit positions for the current date. Each day produces different content for the overview, love, career, health, and finance categories. The response also includes a fresh lucky number, lucky color, and compatible signs list.

Q: Can I fetch horoscopes in languages other than English? A: Yes. Add a lang query parameter to the URL. Supported languages include English (en), Spanish (es), French (fr), German (de), Hindi (hi), Portuguese (pt), Russian (ru), and Turkish (tr). For example: https://roxyapi.com/api/v2/astrology/horoscope/aries/daily?lang=es returns the forecast in Spanish.

Q: Is it possible to send weekly or monthly horoscopes instead of daily? A: Yes. Replace /daily with /weekly or /monthly in the endpoint URL and adjust your Make schedule accordingly. The weekly endpoint returns forecasts with lucky days, lucky numbers, and a week-long outlook. The monthly endpoint includes a week-by-week breakdown, key astrological dates, and monthly lucky numbers.

Q: Can I store horoscope data in a database or spreadsheet instead of sending it? A: Absolutely. Replace the email or Slack module with a Google Sheets, Airtable, or database module. Map the JSON response fields to spreadsheet columns. This is useful for building a horoscope archive, tracking lucky numbers over time, or feeding content into a CMS for a website or app.

Conclusion

Automating daily horoscope delivery with Make and the Western Astrology API takes less than 30 minutes to set up and runs indefinitely with zero maintenance. You get transit-based forecasts with love, career, health, and finance categories, plus lucky numbers and compatible signs, delivered to any channel your audience uses. The all-signs batch endpoint makes it efficient to serve all 12 zodiac signs in a single API call.

Start building your automated horoscope pipeline with the Western Astrology API. Plans start at $39 per month with 5,000 requests included. See pricing.