Chain Two APIs Together
Chain API calls with Nebula's AI agent — pull data from one service and push it to another, like syncing Sentry errors to Notion or analytics to Slack.
What you'll build
Connect two services that don't have a native integration. Pull data from one API, transform it, and push it into another — like syncing Sentry errors into a Notion incident log, or piping PostHog analytics into a Slack summary.
What to say
Pull the latest unresolved errors from Sentry and create a row for each one in our Notion incident tracker.
I'll use your Sentry Monitor Agent (created earlier via the Agent Creator) and your Notion Agent to chain this together.
Delegating to @sentry-monitor-agent to fetch unresolved issues.
Calling sentry-list-unresolved-issues... Found 3 unresolved errors: NullPointerException in payments, TimeoutError in auth service, and ValidationError in signup flow.
Delegating to @notion-agent to create incident rows.
Calling notion-create-page for each error... Created 3 rows in your incident tracker.
Done. Added 3 incidents to your Notion tracker:
- NullPointerException in payments (142 events, first seen 2 hours ago)
- TimeoutError in auth service (89 events, first seen yesterday)
- ValidationError in signup flow (23 events, first seen 3 days ago)
Each row has the error title, event count, first seen date, and a link back to Sentry.
What happens
You connect the source API
Tell Nebula the service and base URL. The Agent Creator creates a dedicated agent for it (like "Sentry Monitor Agent") with action keys like sentry-list-unresolved-issues. A secure credential popup appears for you to enter the API key — it's never entered in the chat. If the destination is already in the Integrations page (like Notion), it already has its own agent.
Nebula delegates to the source agent
Nebula delegates to the source agent, which calls run_action with the right action key to fetch the data you asked for.
Data is transformed to fit the destination
Nebula maps the fields from the source into the format the destination expects. You can tell it exactly what to include or let it figure out a sensible mapping.
Nebula delegates to the destination agent
Nebula delegates to the destination agent (like "Notion Agent") which calls run_action to create the records — Notion rows, Slack messages, spreadsheet entries, or whatever the target service accepts.
More chains to try
Pull our daily active users from PostHog and post a chart to #metrics in Slack every morning.
When a Grafana alert fires, create an incident in PagerDuty with the alert details.
Fetch all published posts from our Ghost blog and add them to a Notion content calendar with their publish dates.
Pull open support tickets from our helpdesk API and post a daily count to #support in Slack.
Make it automatic
Run this Sentry → Notion sync every morning at 9 AM.
Creating scheduled trigger: every day at 9:00 AM UTC. Task: fetch unresolved Sentry errors via Sentry Monitor Agent, create Notion rows via Notion Agent.
Your trigger is live. Every morning at 9 AM, I'll pull unresolved errors from Sentry and sync them to your Notion incident tracker. You can pause or edit this from the Triggers page.
Combine API chaining with a scheduled trigger so the data flows automatically. You can also use a webhook trigger — for example, Sentry can fire a webhook when a new error appears, which triggers the chain immediately.
Connect your integrations
For services in the Integrations page (Notion, Slack, GitHub), use OAuth. For everything else, ask Nebula to set up a custom API connection — a secure popup will appear for you to enter credentials.
Related recipes
Set Up Dashboard Alerts
Set up AI dashboard alerts with Nebula to monitor KPIs daily. Get a Slack notification when signups, revenue, or other metrics cross your thresholds.
Development
Automate development workflows with Nebula recipes — GitHub issue triage, deployment alerts, code review digests, and custom API integrations.