SocialCrawl

Use SocialCrawl with Power Automate

Pull social media data into Power Automate without writing a server.

You can call SocialCrawl from a Power Automate cloud flow with the HTTP action. One GET request returns structured data for later actions. Setup takes three steps: add the action, set the key header, handle the failure.

The HTTP action is a premium connector, so the user who runs the flow needs a Power Automate premium licence. Without one, the run fails with a licensing error.

Before you start

Create an API key in the dashboard under API Keys. Enter it in the HTTP action's header, and turn on Secure inputs and Secure outputs in the action's settings so the run history hides it. Never share a flow screenshot that shows the key. Prove the key with a call that costs nothing:

Check the key (0 credits)
curl "https://www.socialcrawl.dev/v1/credits/balance" \
  -H "x-api-key: sc_your_key_here"

A reply with "success": true and your balance in data.balance means the key works.

Connect

Add an HTTP action and set these fields:

FieldValue
MethodGET
URIhttps://www.socialcrawl.dev/v1/tiktok/profile/videos
Querieshandle = mrbeast
Headersx-api-key = your key

Change the path and the queries to call any other endpoint.

Read the answer

Every response has the same shape. Branch on success. A list puts its rows in data.items, and pagination.next_cursor is the token for the next page.

Response (trimmed)
{
  "success": true,
  "data": { "items": [{ "id": "7654638524729216287" }] },
  "pagination": { "next_cursor": "sc.eyJ2Ijoy…", "has_more": true },
  "credits_used": 1,
  "credits_remaining": 99
}

Read a value with an expression such as body('HTTP')?['data']?['items']. To read the next page, send next_cursor back as the cursor query, and stop when has_more is false. See Pagination.

When it stops

Add a Send an email or Post message action after the HTTP action. In its settings, set Run after to has failed, so it runs only when the call is refused. Put this expression in the message:

Message expression
body('HTTP')?['error']?['message']

When credits run out, the answer is a 402 with error.type set to INSUFFICIENT_CREDITS. Read error.message for the text and error.details.checkout_url for the link that opens checkout. When the link is absent, error.details.top_up_url opens the billing page.

Never retry a 402, because it fails until credits are added. The action's retry policy suits a 429 or a 502, 503 or 504, and not a 402. For a 429, wait the seconds in the Retry-After header. See Errors.

What a run costs

It depends on the endpoint, and some endpoints are priced by what they return. Endpoint pricing lists each one, and Credits explains cache hits and refunds. A recurrence flow calls the API every time it fires. GET /v1/utility/estimate quotes a call for 0 credits.

On this page