PipedreamHQ / PipedreamHQ/pipedream
SocialCrawl
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
### App
SocialCrawl
https://www.socialcrawl.dev/docs
### Sources
No custom trigger is needed for the first release. Users can run searches on a schedule using Pipedream's existing scheduling tools.
### Actions
We're the SocialCrawl team. We'd like your help adding one action to Pipedream: Search Social Web.
SocialCrawl lets users search public conversations across social platforms through one API.
How users would use the action:
1. Connect their SocialCrawl account using their own API key.
2. Enter a topic, brand or keyword, with optional platform and date filters.
3. Get ranked search results with links to the original sources, ready to use in later workflow steps.
Example workflow:
A research team searches for recent conversations about a brand each week, then saves the results to Google Sheets. This gives them a repeatable way to collect research without manually searching each platform.
What we need from Pipedream:
Help us build, test and publish this action for Pipedream Workflows. We'd like to start with this one action and expand later. We can arrange a dedicated test account through a secure process.
Technical reference:
API: GET https://www.socialcrawl.dev/v1/search/everywhere
Authentication: x-api-key header
Our documentation recommends a 60-second request timeout for full searches.
Docs: https://www.socialcrawl.dev/docs
OpenAPI: https://www.socialcrawl.dev/v1/openapi.json
Contact: Oscar Lee, admin@ridiocompany.com
Contributor guide
Research direction
Start by reviewing Pipedream's existing action integrations and the SocialCrawl API documentation or OpenAPI specification. Implement and test the Search Social Web action with x-api-key authentication, search and filter inputs, ranked results, and the documented 60-second timeout. Done means the action is tested and ready to publish in Pipedream Workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, openapi
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100