> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Farcaster User Followers

Get the list of followers for a Farcaster user by FID. Returns follower profiles with engagement metrics and power badge status. Supports pagination. Ideal for: airdrop targeting, community analysis, follower reward programs, social graph exploration.

![Get Farcaster User Followers logo](https://ai-icon.b3.fun/logo/farcaster)
Catalog action Social

Get the list of followers for a Farcaster user by FID. Returns follower profiles with engagement metrics and power badge status. Supports pagination. Ideal for: airdrop targeting, community analysis, follower reward programs, social graph exploration.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `get-farcaster-user-followers` |
| Category | Social |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `social`, `farcaster`, `neynar`, `followers`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `fid` | `number` | Yes | Farcaster user ID \(FID\) to get followers for |
| `limit` | `number` | No | Maximum number of followers to return \(default: 25, max: 100\) |
| `cursor` | `string` | No | Cursor for pagination \(from nextCursor in previous response\) |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `followers` | `array` | Yes | Array of followers |
| `nextCursor` | `string \| null` | No | Cursor for next page of results |

## Examples

**Workflow node**

```json
{
  "type": "get-farcaster-user-followers",
  "payload": {
    "fid": 1
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/get-farcaster-user-followers/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "fid": 1
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.