Integration
Connect Raindrop.io to APIs.guru
When something happens in Raindrop.io, your agent does the next thing in APIs.guru. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Raindrop.io and APIs.guru to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Raindrop.io and APIs.guru
Triggers and actions 4 triggers ยท 7 actions
Trigger
New Favorited ItemTriggers when you favorite an item.
- New Item
Triggers when a new item is created.
- New Item Moved to Collection
Triggers when an item moved to collection.
- New Tagged Item
Triggers when you tag an item.
- Create Item
Creates an Item
Action
Find APIs by providerReturns all APIs listed for a given provider. GET /{provider}.json (provider input path param)
- Find service names by provider
Returns all serviceNames registered for a given provider (providers that host multiple APIs under sub-services). GET /{provider}/services.json (provider input path param)
- Get API metrics
Returns basic aggregate metrics about the APIs.guru directory (numSpecs, numAPIs, numEndpoints, etc). GET /metrics.json
- Get API specification
Retrieves one version of a particular API's OpenAPI spec by provider and api version, optionally scoped to a serviceName. GET /specs/{provider}/{api}.json or /specs/{provider}/{service}/{api}.json (provider, api, optional service input params)
- List APIs
Returns the full catalog of all APIs indexed by APIs.guru, keyed by provider/api. GET /list.json
- List providers
Returns the full list of API providers known to APIs.guru. GET /providers.json
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.