Gravity Input

Overview

This node listens for real-time messages published on a specified Redis channel via the Gravity event system. It acts as a trigger that activates workflows whenever new events arrive from the Gravity platform. This is useful for integrating external event streams into n8n, enabling automation based on live data such as notifications, alerts, or updates pushed through Gravity.

Practical examples include:

• Triggering a workflow when a new user activity event is published.
• Reacting to system alerts or monitoring data sent through Gravity.
• Processing custom application events streamed in real-time.

Properties

Output

The node outputs an array of JSON objects representing the received messages from the subscribed Gravity channel. Each output item corresponds to one event payload, containing the data sent by Gravity.

If an error occurs while processing a message, the output will contain an object with an error field describing the issue and the original message under originalMessage.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential for authenticating with the Gravity server.
• Connects to the Gravity event bus service using the provided server URL and API key.
• Subscribes to a Redis channel managed by Gravity to receive events.

Troubleshooting

• Connection issues: Ensure the Gravity server URL and API key are correctly configured and valid.
• Subscription failures: Verify the specified Redis channel exists and is accessible.
• Message processing errors: If the node emits error objects, check the error message for details. Common causes include malformed event payloads or unexpected data formats.
• Credential problems: Missing or invalid credentials will prevent connection to Gravity and cause errors during subscription.

Links and References

• Gravity AI Developer Documentation (for API and event bus usage)
• Redis Pub/Sub Concepts (background on Redis channels)