Skip to main content
TL;DR: Edges uses Identities (your users) connected to Integrations (LinkedIn accounts) to run Actions. That’s it.

​
How Edges Works

​
Identities vs. Workspace Members

Edges distinguishes between two types of users:

​
Workspace Member Roles

​
What is an Identity?

An Identity represents an end user in your SaaS or AI agent platform. Identities:
  • Execute automated Actions on your behalf
  • Connect to Integrations (like LinkedIn)
  • Have no access to the Edges dashboard
  • Are ideal for mapping your users to integration accounts
When do you need Identities? Only for actions that require being “logged in” — sending messages, accepting invitations, etc. For generic enrichment, use Managed Mode instead.

​
Identity Modes

Control how accounts execute your Actions:
See the Quickstart for code examples of each mode.

​
Managing Identities

1

Create an Identity

Use the Create Identity API or the Identities page.
2

Connect an Integration

Link a LinkedIn account via Chrome Extension, API authentication, or cookies.
3

Execute Actions

Use identity_ids in your API calls to specify which Identity runs the Action.
Licensing: Identity seats are included in your plan. Check Pricing for your allocation. Contact sales@edges.run for higher limits.

​
Identity Security

Every Identity is assigned a unique IP address for enhanced security. Learn more about Identity management and security.

​
Integrations

An Integration connects an Identity to an external service (LinkedIn, Sales Navigator, etc.).
  • Each Integration belongs to one Identity
  • Integrations authenticate your requests with third-party APIs
  • Multiple Integrations can connect to the same Identity (e.g., LinkedIn + Sales Navigator)

​
LinkedIn Integrations

Smart Limits

How Edges protects your accounts

LinkedIn Licenses

What’s supported

Sync, Rent, or Managed

Choose your approach

Best Practices

Avoid rate limits

​
LinkedIn Webhooks

Get real-time notifications when account status changes:
Webhooks are essential for maintaining reliable integrations. See setup instructions.

​
Execution Modes

Edges supports three ways to run Actions:

Live Mode — Real-time results

  • Response: Immediate (synchronous)
  • Use case: Single requests, real-time enrichment
  • Endpoint: /run/live
Best for most use cases due to simplicity.
  • Response: Run ID immediately, results via callback
  • Use case: Batch processing, large datasets
  • Endpoint: /run/async
Ideal when processing thousands of records or when real-time isn’t required.See Async & Callbacks for implementation details.
  • Response: Schedule ID, results via callback on each run
  • Use case: Recurring tasks, campaigns, off-peak processing
  • Endpoint: /run/schedule
Define schedule_at, cron, and timezone for precise timing.See Schedules for CRON examples.

​
Data Model

For developers building deep integrations, here’s the database schema showing entity relationships:

Database schema: Identities, Integrations, Runs, and their relationships

Interactive version: View full diagram

​
What’s next?

Set Up Identities

Create and manage your first Identity

Connect LinkedIn

Link a LinkedIn account to an Identity

Browse Actions

Explore 60+ available Actions

TypeScript SDK

Type-safe SDK for faster development