A2A Net
Book a demo

LeadSimple One AI Agent

LeadSimple One is a property management workspace that property management teams use to manage owner and resident relationships, communications, leasing, recurring operations, and reporting.

A2A Net isn't affiliated with LeadSimple One. Checked . Recheck

Chat with the LeadSimple One agent

LeadSimple One helps property management teams keep growth, conversations, leasing, and day-to-day operations connected around owners, residents, prospects, properties, and work. - Find contacts, deals, properties, units, conversations, calls, text activity, tasks, and users. - See where deals and operational processes sit, who owns them, and which stages or steps come next. - Create or update contacts, deals, processes, property details, units, notes, and conversation status. - Record call and text activity while keeping it associated with the right people and work. - Run reports on deal status, aging, cost or value, follow-up persistence, and time to contact or close. - Organize assignments, tags, relationships, custom fields, files, and webhook subscriptions. For example: “Find the open deals in my owner-acquisition pipeline that have not been updated recently, group them by stage, and tell me where attention is needed.”

LeadSimple One and AI

In-app AI

AI assistant

Source

Accessible to AI

5 / 5

LeadSimple One has an MCP server, so AI assistants can connect to it directly.

AI value

5.0 / 5

Data users create and update
5
Data users look up and analyze
5
How often it's used
5
Text-friendly data
5

What the agent can do

Accounts

  • get_accounts — ENTERPRISE ONLY: Returns a list of company accounts under your enterprise.
  • get_accounts_account_id — ENTERPRISE ONLY: Returns an individual company account.

Calls

  • get_calls — Use this to list call activity records for the account. It supports pagination, filtering by update time, and optionally including custom fields; requesting custom fields can reduce the page size and increase response time.
  • post_calls — Use this to record an inbound or outbound call activity and associate it with the phone participants. Provide the from and to numbers, and optionally include duration, timestamps, outcome, description, recording URL, or the participating LeadSimple user. This records the call in LeadSimple; it does not place a call.
  • patch_calls_call_id — Use this to correct or replace the description on an existing call activity identified by its call ID. It does not place a call or change the call's participants.

Contacts

  • get_contacts — Returns a list of contacts on the account
  • post_contacts — Create a contact
  • put_contacts_contact_id — Use this to update supported fields on an existing contact identified by contact ID, including name, company, email addresses, phone numbers, mailing address, secondary name, and tags. Use an ID read from the API and send only the intended changes.

Conversations

  • get_conversations — Returns a list of conversations on the account, respecting User permissions
  • get_conversations_allowed_tags — Returns a list of available tags for conversations
  • patch_conversations_conversation_id — Use this to change an existing conversation's status, assignee, or snooze setting. When setting the status to snoozed, supply the required snoozed-until time. Use a conversation ID returned by the API.
  • patch_conversations_conversation_id_tag — Tag a conversation

Current account

  • get_current_account_custom_fields — List custom_fields available on account optionally filtered by category

Custom fields

  • get_custom_fields — Returns a list of custom fields on the account
  • post_custom_fields — Use this to define a new custom field for a contact, property, unit, deal, or process. Supply its category, data type, and label, and optionally its options and pipeline or process-type associations. This creates the field definition; it does not populate a value on an existing record.

Deals

  • get_deals — Returns a list of deals on the account filterable by pipeline, name, email, or phone number
  • post_deals — Use this to create a deal in a specified pipeline, optionally including contact and property information plus stage, source, assignee, tags, value, cost, unit count, dates, comments, and marketing attribution. Before calling it, read available pipelines and, when needed, stages and sources, and check for an existing matching deal so duplicates are not created accidentally.
  • get_deals_deal_id — Returns an individual deal.
  • put_deals_deal_id — Use this to update an existing deal by ID. It can change supported deal details, pipeline or stage, assignee, comments, dates, value, cost, tags, and related contact, property, or unit IDs. Use a stage ID read from the API when moving the deal, and use remove_tags only when the user explicitly wants supplied tags removed.

Info

  • get_info_account — Info about the current account
  • get_info_user — Info about the current user

Notes

  • post_notes — Use this to add an activity note to a specific deal or process. Provide the parent ID and whether the parent is a Deal or Process, plus the note text; optionally include its kind, direction, creation time, or user. It adds a note and does not alter the parent record's stage or fields.

Pipelines

  • get_pipelines — Returns a list of pipelines on the account
  • get_pipelines_pipeline_id — Returns an individual pipeline.
  • get_pipelines_pipeline_id_custom_fields — List custom fields available on a pipeline
  • get_pipelines_pipeline_id_deals — List deals under a pipeline
  • get_pipelines_pipeline_id_deals_deal_id — Returns an individual deal.
  • get_pipelines_pipeline_id_sources — List sources under a pipeline
  • get_pipelines_pipeline_id_stages — List workflow stages under a pipeline
  • get_pipelines_pipeline_id_stages_stage_id — Returns an individual stage.
  • get_pipelines_pipeline_id_stages_stage_id_steps — List steps within an individual stage
  • get_pipelines_pipeline_id_users — List users who have access to a pipeline

Process types

  • get_process_types — Returns a list of process type on the account
  • get_process_types_process_type_id — Returns an individual process type.
  • get_process_types_process_type_id_assignee_roles — List assignee roles under a process type
  • get_process_types_process_type_id_contact_roles — List contact roles under a process type
  • get_process_types_process_type_id_custom_fields — List custom_fields available on a process type
  • get_process_types_process_type_id_processes — List processes under a process_type
  • get_process_types_process_type_id_processes_process_id — Returns an individual process.
  • get_process_types_process_type_id_stages — List workflow stages under a process type
  • get_process_types_process_type_id_stages_stage_id — Returns an individual stage.
  • get_process_types_process_type_id_stages_stage_id_steps — List steps within an individual stage
  • get_process_types_process_type_id_users — List users who have access to a process type

Processes

  • get_processes — Returns a list of processes on the account filterable by process type
  • post_processes — Use this to create an operational process in a specified process type and stage. It can optionally set a name, due date, comments, tags, assignee and role assignments, and associate contacts, properties, or units. Read the process type, stage, role, and related record IDs first rather than guessing them.
  • get_processes_process_id — Returns an individual process.
  • put_processes_process_id — Use this to update an existing process by ID, including its name, due date, comments, close time, assignee, tags, stage, and user-role assignments. Use a stage ID read from the matching process type when moving the process, and use remove_tags only for an intentional tag removal.

Properties

  • get_properties — Returns a list of properties on the account
  • get_properties_property_id — Returns an individual property.
  • put_properties_property_id — Use this to update an existing property by property ID. Supported changes include address fields, property type, and tags; it does not create a new property or update its units.
  • get_properties_property_id_units — List units under a property
  • put_properties_property_id_units_unit_id — Updates a unit

Property groups

  • get_property_groups — Returns a list of property groups on the account

Reports

  • post_reports_deal_aging — Use this read-only report to summarize the age of deals matching optional created, closed, last-touched, and status filters, grouped by the requested dimension. It is useful for finding how long deals have remained open or comparing deal age across users or sources; provide group_by.
  • post_reports_deal_cost — Use this read-only report to roll up deal cost or value for deals matching optional date and status filters. Provide the requested metric and grouping dimension to compare results across users or sources.
  • post_reports_deal_cost_by_month — Use this read-only report to summarize deal costs month by month for a specified year, with optional date and status filters and grouping by the requested dimension. It is useful for comparing monthly acquisition or deal-cost trends.
  • post_reports_deal_persistence — Use this read-only report to count follow-up attempts for filtered deals. Provide the field to measure and grouping dimension, and use optional date and status filters to compare follow-up persistence across users or sources.
  • post_reports_deal_status — Use this read-only report to count matching deals by status and group the counts by the requested dimension, such as user, source, or stage. Apply optional created, closed, last-touched, and status filters when a narrower view is needed.
  • post_reports_deal_time_to_close — Use this read-only report to summarize elapsed time to close for filtered deals, grouped by the requested dimension. Apply date and status filters to compare closing speed across users or sources.
  • post_reports_deal_time_to_contact — Use this read-only report to summarize elapsed time for filtered deals using the required field, grouped by the requested dimension. It is useful for analyzing contact or response timing when the selected field identifies the relevant milestone.

Tasks

  • get_tasks — Use this to list account tasks, optionally narrowing results by due type, step IDs, update time, custom fields, or property groups. Use pagination for larger result sets and request expanded fields only when needed.

Text messages

  • get_text_messages — Returns a list of text messages on the account
  • post_text_messages — Use this to record an inbound or outbound text-message activity and associate it with sender and recipient numbers and, optionally, a participating user, timestamp, or description. This records the message in LeadSimple; it does not send an SMS.
  • get_text_messages_text_message_id — Returns a single text message
  • patch_text_messages_text_message_id — Use this to update the description of an existing text-message activity identified by its text-message ID. It does not send a message or change its participants.

Uploaded files

  • post_uploaded_files — Use this to upload and associate a file with a specific deal or process. Provide the parent ID and parent type, and set public_access only after the user understands that anyone with the private URL could download the file without authentication.

Users

  • get_users — Returns a list of users on the account

Webhook subscriptions

  • get_webhook_subscriptions — List all webhook subscriptions for the current account
  • post_webhook_subscriptions — Use this to create a webhook subscription that sends selected account events to a target URL. Confirm the exact event and destination before creating it.
  • get_webhook_subscriptions_webhook_subscription_id — Returns an individual webhook subscription.
  • put_webhook_subscriptions_webhook_subscription_id — Use this to change the event or target URL of an existing webhook subscription by ID. Confirm the resulting event and destination before updating it.

AI in LeadSimple One's categories

Real Estate CRM 1 checked · average AI value 5.0
  • AI assistant 100%
  • AI features 0%
  • No AI found 0%

FAQs

Yes. LeadSimple One has an AI assistant that users can ask questions or give tasks to.

Yes. LeadSimple One's API is documented at https://docs.leadsimple.com/openapi.json.

Yes. LeadSimple One's MCP server is at https://api.leadsimple.com/mcp.

Chat with A2A Net's LeadSimple One agent on this page. It works in your LeadSimple One account, with your LeadSimple One credentials, and you can add it to Slack, Microsoft Teams and more.

No. A2A Net isn't affiliated with LeadSimple One. This page describes what A2A Net found on LeadSimple One's website.

Work at LeadSimple One? Claim or remove this page