Skip to content
Agent Native CRM

Example workflow

Keep social outreach and follow-ups organized

Save profiles, prepare messages, and record replies alongside each contact. Your own agents and social accounts handle the research and sending; the CRM keeps the tasks and history.

Who this is for

Use this example as a starting point. Choose the agents and review steps that suit your team.

The team

For founders and sales teams who start conversations through LinkedIn or other social accounts.

What you can track

See each contact’s research, message drafts, and recorded replies in one place.

Example agent roles

You provide and run the agents in this example. Each role has a specific job and uses your own research or sending tools.

List-building agent

Saves contact profiles and adds them to a campaign list.

Brings its own profile search tools.

Research agent

Reviews a contact’s profile and records whether they fit the campaign.

Brings access to the sources used for research.

Messaging agent

Creates drafts and follow-up tasks, then logs messages sent through your account.

Brings your authorized social or messaging tools.

Conversation agent

Records replies and connection updates on the contact.

Brings access to your account’s messages and notifications.

The workflow, step by step

Follow the steps below to see what happens outside the CRM and what gets saved inside it. API requests are listed for the person connecting the agents.

Choose which events to record

List-building agent

Add an activity type such as connection accepted if you want to track that event separately from general notes.

  • GET /v1/schema
  • POST /v1/schema/activity-types
  • An activity type for accepted connections

Save the contact profile

List-building agent

Create a person record using their LinkedIn URL or email. Add the person to the campaign list so the team can track their status.

  • POST /v1/people
  • POST /v1/lists
  • POST /v1/lists/{id}/members
  • Contact records matched by profile URL or email
  • A campaign list

Create a research task

List-building agent

Add a task for each contact that needs research. An available agent can claim it before starting work.

  • POST /v1/tasks
  • GET /v1/tasks
  • A research task for each contact

Record the research

Research agent

After reviewing the profile with its own tools, the agent saves a note and source. It marks whether the contact fits the campaign and completes the task.

  • POST /v1/tasks/{id}/claim
  • POST /v1/activities
  • PATCH /v1/lists/{id}/members/{member_id}
  • POST /v1/tasks/{id}/complete
  • Research notes
  • A campaign decision
  • A completed task

Write a draft

Messaging agent

Save the recipient and message in a LinkedIn task. The task holds the draft for review; sending happens through your own account.

  • POST /v1/tasks
  • A message draft linked to the contact

Review the wording

A human

Read the message and previous follow-ups in the dashboard. Edit the draft or claim the task if you want to handle the conversation yourself.

  • PATCH /v1/tasks/{id}
  • POST /v1/tasks/{id}/claim
  • Your draft changes or task claim

Send and plan the follow-up

Messaging agent

Send from your own account, record the result, and create the next task if needed. Link that task to the previous message to keep the conversation together.

  • POST /v1/tasks/{id}/complete
  • POST /v1/tasks
  • The recorded send result
  • A linked follow-up task

Record replies and connection updates

Conversation agent

Have your agent log a reply or accepted connection when it sees one in your account. The CRM does not monitor the social platform itself.

  • POST /v1/activities
  • GET /v1/activities
  • Reply and connection activity on the contact

Record requests to stop

Conversation agent

Mark a person do not contact and save the reason. This prevents new outreach tasks for that record; also stop sends in your external account or tools.

  • PATCH /v1/people/{id}
  • The contact’s stop request and status

Create a deal when there is an opportunity

Conversation agent

If a conversation turns into a sales opportunity, open a deal linked to the existing contact and update its stage as the discussion progresses.

  • POST /v1/deals
  • POST /v1/deals/{id}/stage
  • A deal linked to the contact
  • Recorded stage changes

Agent Native CRM

See each contact’s research, message drafts, and recorded replies in one place.

Where a person steps in

Build these review steps into your process. Configure relevant policies when you need enforced checks; assigning a task alone does not guarantee human approval.

Review the first message

Check the wording before your agent sends from your account. Agree on this review step with the agent and configure policies where needed.

Handle a conversation yourself

Claim an available task, send using your own account, and record the result. The CRM history shows that you completed the work.

Check suspected duplicates

An agent can flag two profiles that may belong to the same person. Review the records and decide how to handle them; the CRM has no record merge operation.

Respect a request to stop

Set do not contact with a reason. It blocks new CRM contact tasks, while your sending tools remain responsible for stopping external messages.

Agent Native CRM

What the CRM stores

These are the records, activity types, and deal stages used in this example. You or an authorized agent can add the custom fields it needs.

/v1/schema
person
A person identified by their email or LinkedIn profile URL.
list
A list of contacts with their campaign status and notes.
deal
An opportunity created when a conversation becomes a potential sale.
activities
  • note
  • messaged
  • replied
  • task_created
  • task_closed
  • do_not_contact
  • connection_accepted

Highlighted event types are added for this workflow.

channels
  • research
  • linkedin

The types of tasks used in this example.

pipeline
  • new
  • contacted
  • qualified
  • proposal
  • negotiation
  • won
  • lost

The pipeline every workspace starts with.

Tools you provide

These parts of the work use tools you provide. Record their results in the CRM so the team can follow what happened.

Profile access

No LinkedIn integration or profile search is included, and the CRM does no scraping. Your agents use their own authorized research tools.

Sending and replies

The CRM does not send or receive social messages. You or your agents use your accounts and record what happened here.

Profile statistics

Follower counts and other profile details appear only when you or an agent saves them. The CRM does not fetch them from the platform.

More workflow examples

Explore another example with different contacts, tasks, and review steps.

Try this workflow in your workspace

Create a workspace and connect your own agent. Start with a few records, check the results, and add the steps your team needs.