curl --request POST \
--url https://api.edges.run/v1/actions/linkedin-extract-page-followers/run/schedule \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"cron": "<string>",
"inputs": [
{
"linkedin_company_url": "<string>",
"custom_data": {}
}
],
"callback": {
"url": "https://example.com/callback",
"headers": {},
"on": "all"
},
"parameters": {},
"name": "<string>",
"identity_ids": [
"44444444-4444-4444-4444-444444444444"
],
"timezone": "<string>",
"schedule_at": "2023-11-07T05:31:56Z"
}
'const options = {
method: 'POST',
headers: {'X-API-Key': '<api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({
cron: '<string>',
inputs: [{linkedin_company_url: '<string>', custom_data: {}}],
callback: {url: 'https://example.com/callback', headers: {}, on: 'all'},
parameters: {},
name: '<string>',
identity_ids: ['44444444-4444-4444-4444-444444444444'],
timezone: '<string>',
schedule_at: '2023-11-07T05:31:56Z'
})
};
fetch('https://api.edges.run/v1/actions/linkedin-extract-page-followers/run/schedule', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.edges.run/v1/actions/linkedin-extract-page-followers/run/schedule"
payload = {
"cron": "<string>",
"inputs": [
{
"linkedin_company_url": "<string>",
"custom_data": {}
}
],
"callback": {
"url": "https://example.com/callback",
"headers": {},
"on": "all"
},
"parameters": {},
"name": "<string>",
"identity_ids": ["44444444-4444-4444-4444-444444444444"],
"timezone": "<string>",
"schedule_at": "2023-11-07T05:31:56Z"
}
headers = {
"X-API-Key": "<api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"schedule_uid": "<string>",
"status": "ACTIVE",
"cron": "<string>",
"timezone": "<string>",
"next_execution_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z"
}{
"error_label": "<string>",
"error_scope": "input",
"error_ref": "ERR-12345",
"message": "<string>",
"status_code": 123,
"params": {},
"data": {}
}{
"error_label": "<string>",
"error_scope": "input",
"error_ref": "ERR-12345",
"message": "<string>",
"status_code": 123,
"params": {},
"data": {}
}{
"error_label": "<string>",
"error_scope": "input",
"error_ref": "ERR-12345",
"message": "<string>",
"status_code": 123,
"params": {},
"data": {}
}Extract LinkedIn Page Followers Schedule
Schedule extraction of LinkedIn company page followers at a specific time or on a recurring basis.
curl --request POST \
--url https://api.edges.run/v1/actions/linkedin-extract-page-followers/run/schedule \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"cron": "<string>",
"inputs": [
{
"linkedin_company_url": "<string>",
"custom_data": {}
}
],
"callback": {
"url": "https://example.com/callback",
"headers": {},
"on": "all"
},
"parameters": {},
"name": "<string>",
"identity_ids": [
"44444444-4444-4444-4444-444444444444"
],
"timezone": "<string>",
"schedule_at": "2023-11-07T05:31:56Z"
}
'const options = {
method: 'POST',
headers: {'X-API-Key': '<api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({
cron: '<string>',
inputs: [{linkedin_company_url: '<string>', custom_data: {}}],
callback: {url: 'https://example.com/callback', headers: {}, on: 'all'},
parameters: {},
name: '<string>',
identity_ids: ['44444444-4444-4444-4444-444444444444'],
timezone: '<string>',
schedule_at: '2023-11-07T05:31:56Z'
})
};
fetch('https://api.edges.run/v1/actions/linkedin-extract-page-followers/run/schedule', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.edges.run/v1/actions/linkedin-extract-page-followers/run/schedule"
payload = {
"cron": "<string>",
"inputs": [
{
"linkedin_company_url": "<string>",
"custom_data": {}
}
],
"callback": {
"url": "https://example.com/callback",
"headers": {},
"on": "all"
},
"parameters": {},
"name": "<string>",
"identity_ids": ["44444444-4444-4444-4444-444444444444"],
"timezone": "<string>",
"schedule_at": "2023-11-07T05:31:56Z"
}
headers = {
"X-API-Key": "<api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"schedule_uid": "<string>",
"status": "ACTIVE",
"cron": "<string>",
"timezone": "<string>",
"next_execution_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z"
}{
"error_label": "<string>",
"error_scope": "input",
"error_ref": "ERR-12345",
"message": "<string>",
"status_code": 123,
"params": {},
"data": {}
}{
"error_label": "<string>",
"error_scope": "input",
"error_ref": "ERR-12345",
"message": "<string>",
"status_code": 123,
"params": {},
"data": {}
}{
"error_label": "<string>",
"error_scope": "input",
"error_ref": "ERR-12345",
"message": "<string>",
"status_code": 123,
"params": {},
"data": {}
}1 credit per 40 results · credit_ratio 0.025 · Credit costs
Company enrichments 10,000 / 24 h · Action limits
Agent skill
edges-linkedin-extract-page-followers — ready-made instructions for coding agents calling this endpoint.Free with Engagement Mode
X-AUTO-PAGINATE header, iterating over all pages of results and sending batches to your callback URL.
You can limit the total number of results with the parameters.max_results param (see “Body” section).sync_mode: "incremental" in the parameters object. Requires an Engagement Identity.- The first iteration performs a full sync (limited by
max_results). - Each subsequent scheduled iteration automatically returns only new data since the last retrieval.
- If the previous run is still in progress when the next iteration triggers, that iteration will be skipped.
- See the Incremental Sync guide for details and limitations.
async and schedule modes deliver results via the callback URL provided in your request.Consistent Format: All execution modes use the same action logic, so inputs and results are identical regardless of mode.Error Handling: Errors follow the standard API error format.async and schedule modes, you have to implement some kind of callback management. Be sure to check the Managing Callbacks guide to better understand how it works and what your can do.Authorizations
Body
- Option 1
- Option 2
Cron expression for scheduling the action. If provided, the action will be scheduled to run at the specified intervals.
1 - 2561 - 100 elements- Option 1
- Option 2
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Optional user-defined label for the run.
255An array of Identity UUIDs linked to identities (e.g. LinkedIn) used to execute the Action. You must provide at least one valid UID with access to the integration. Do not use account_uid values — only user_uid is supported.
["44444444-4444-4444-4444-444444444444"]
The timezone to use for the cron expression (IANA timezone format, e.g., "America/New_York" or "Europe/Paris"). If not provided, the UTC timezone will be used.
1 - 64This is for one shot or 1st programmation calls. If not provided, the run will be scheduled immediately.
Callbacks
POST{$request.body#/callback/url}onSave
Body
Stable callback identifier (remains identical across retries). Used by clients for deduplication.
Show child attributes
Show child attributes
- Option 1
- Option 2
Show child attributes
Show child attributes
Represents an error returned by the API. This schema defines the standard structure of error messages to ensure consistent error handling across the application.
Show child attributes
Show child attributes
Number of results included in this callback.
Results of the current callback
Show child attributes
Show child attributes
Response
Callback successfully processed
Response
Default Response
The UID of the scheduled run.
The status of the scheduled run.
ACTIVE, CANCELLED, PAUSED, COMPLETED Cron expression for the scheduled run (POSIX format)
Timezone for the scheduled run (IANA timezone format)
Next execution at
The date and time when the run was created.

