Skip to main content
POST
/
actions
/
salesnavigator-extract-messages
/
run
/
schedule
Schedule salesnavigator-extract-messages action
curl --request POST \
  --url https://api.edges.run/v1/actions/salesnavigator-extract-messages/run/schedule \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "cron": "<string>",
  "inputs": [
    {
      "sales_navigator_thread_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"
}
'
{
  "schedule_uid": "<string>",
  "status": "ACTIVE",
  "cron": "<string>",
  "timezone": "<string>",
  "next_execution_at": "2023-11-07T05:31:56Z",
  "created_at": "2023-11-07T05:31:56Z"
}

Documentation Index

Fetch the complete documentation index at: https://docs.edges.run/llms.txt

Use this file to discover all available pages before exploring further.

Free with Engagement Mode

No credits required when executed with an Engagement Identity. Set type: “engagement” when creating an Identity via API.
To run LinkedIn actions, you must first create an identity and connect a LinkedIn account, either using our Chrome Extension, username/password login, or Managed Accounts for a hassle-free setup.

Authorizations

​
X-API-Key
string
header
required

Body

application/json
​
cron
string
required

Cron expression for scheduling the action. If provided, the action will be scheduled to run at the specified intervals.

Required string length: 1 - 256
​
inputs
object[]
required
Required array length: 1 - 100 elements
​
callback
object
required
​
parameters
object
​
name
string | null

Optional user-defined label for the run.

Maximum string length: 255
​
identity_ids
string<uuid>[] | null

An 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.

Example:
["44444444-4444-4444-4444-444444444444"]
​
timezone
string

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.

Required string length: 1 - 64
​
schedule_at
string<date-time>

This is for one shot or 1st programmation calls. If not provided, the run will be scheduled immediately.

Response

Default Response

​
schedule_uid
string

The UID of the scheduled run.

​
status
enum<string>

The status of the scheduled run.

Available options:
ACTIVE,
CANCELLED,
PAUSED,
COMPLETED
​
cron
string | null

Cron expression for the scheduled run (POSIX format)

​
timezone
string | null

Timezone for the scheduled run (IANA timezone format)

​
next_execution_at
string<date-time> | null

Next execution at

​
created_at
string<date-time>

The date and time when the run was created.