AstrologyInstall

Summary

Computes relationship timing insights for two people by sending both subjects' birth data and a date range to the Astrology API, returning astrological timing/transit analysis for the relationship over that period.

Inputs

• year (required) — Birth year of the first person (e.g., 1990).
• month (required) — Birth month of the first person, 1-12.
• day (required) — Birth day of the first person, 1-31.
• hour (required) — Birth hour of the first person in 24-hour format, 0-23.
• minute (required) — Birth minute of the first person, 0-59.
• locationType (required) — How to specify the first person's birth location: city name or exact coordinates.
• city (required) — First person's birth city; required when locationType is 'city'.
• countryCode (required) — 2-letter ISO country code for the first person's birth city; required when locationType is 'city'.
• latitude (required) — First person's birth latitude in decimal degrees; required when locationType is 'coordinates'.
• longitude (required) — First person's birth longitude in decimal degrees; required when locationType is 'coordinates'.
• subject2Name — Optional name for the second person, used in report titles.
• subject2Year (required) — Birth year of the second person.
• subject2Month (required) — Birth month of the second person, 1-12.
• subject2Day (required) — Birth day of the second person, 1-31.
• subject2Hour (required) — Birth hour of the second person in 24-hour format, 0-23.
• subject2Minute (required) — Birth minute of the second person, 0-59.
• subject2LocationType (required) — How to specify the second person's birth location: city name or exact coordinates.
• subject2City (required) — Second person's birth city; required when subject2LocationType is 'city'.
• subject2CountryCode (required) — 2-letter ISO country code for the second person's birth city; required when subject2LocationType is 'city'.
• subject2Latitude (required) — Second person's birth latitude; required when subject2LocationType is 'coordinates'.
• subject2Longitude (required) — Second person's birth longitude; required when subject2LocationType is 'coordinates'.
• startDate (required) — Start date for the transit analysis period, in YYYY-MM-DD format.
• endDate (required) — End date for the transit analysis period, in YYYY-MM-DD format.
• language — Language for response text and interpretations. Options: en, ru, de, es, fr, it, pt, zh, ja, ko. Default: en.
• simplify — When true, returns a simplified response with key data only. When false, returns the full API response with all metadata. Default: true.

Output shape

JSON object from the Astrology API. If simplify is true, the response is reduced to a subset of top-level fields (nested objects preserved). If simplify is false, the complete API response is returned.

Returns the Insights API response for relationship timing. With simplify enabled, only key top-level fields are returned; with simplify disabled, the full API response including metadata is returned.

Examples

Example 1: Determine favorable or challenging timing windows for a relationship over a given date range by comparing two people's birth charts.

Insights → Relationship: Timing

Links

• n8n community nodes installation guide