Actions115
- Profiles Actions
- Posts Actions
- Media Actions
- Social Accounts Actions
- Connect Platform Actions
- Get Connect URL
- Complete OAuth Callback
- List Facebook Pages (Headless)
- Select Facebook Page (Headless)
- List Google Business Locations (Headless)
- Select Google Business Location (Headless)
- Get Pending OAuth Data (Headless)
- List LinkedIn Organizations (Details)
- Select LinkedIn Organization
- List Pinterest Boards (Headless)
- Select Pinterest Board (Headless)
- List Snapchat Profiles (Headless)
- Select Snapchat Profile (Headless)
- Connect Bluesky via Credentials
- Connect WhatsApp via Credentials
- Generate Telegram Code
- Connect Telegram Directly
- Check Telegram Status
- Usage Statistics Actions
- Facebook Management Actions
- LinkedIn Management Actions
- Clone Connection Actions
- Webhooks Actions
- Queue Actions
- Account Groups Actions
- Analytics Actions
- Bluesky Management Actions
- Pinterest Management Actions
- Reddit Management Actions
- Telegram Management Actions
- Google Business Management Actions
- Snapchat Management Actions
- Invites Actions
- Logs Actions
- API Keys Actions
- Users Actions
- Tools Actions
Tools → Bluesky: Download
AI-generatedSummary
Downloads and returns the content of a specified Bluesky post given its URL.
Inputs
- URL (required) — The URL of the Bluesky post to download.
- Request Options — Optional HTTP request settings such as batching, SSL verification override, proxy configuration, and timeout in milliseconds.
Output shape
a single record containing the downloaded post data typically in JSON format
The output includes the full response from the Bluesky download endpoint. Request options can affect behavior like timeout, proxy, and SSL validation. Batching settings apply only if multiple URLs are input (not shown here). Error handling details are consistent with the node's default response behaviors.
Examples
Example 1: Download a Bluesky post by its URL
Provide the Bluesky post URL in the 'URL' field; optionally configure request options such as timeout or proxy; upon execution, the node fetches the post content and returns it for subsequent workflow steps.