Close CRM
Access your Close CRM data. Understand your leads, get deeper insights, and make them actionable.
Access your Close CRM data. Understand your leads, get deeper insights, and make them actionable. This plugin allows you to retrieve information about leads, contacts, opportunities, tasks, activities, and addresses stored in Close CRM. You can search for specific records based on various fields, such as name, status, phone, and email. The plugin also provides details about activities including calls, emails, meetings, notes, and SMS. With Close CRM plugin, you can effectively manage your sales process, track customer interactions, and streamline your communication with leads and contacts.
How to
Comments (0)
API docs
Learn how to use Close CRM effectively! Here are a few example prompts, tips, and the documentation of available commands.
Example prompts
-
Prompt 1: "Find all the recent leads related to the sales pipeline."
-
Prompt 2: "Give me a summary of the activities for Lead ID 12345."
-
Prompt 3: "Search for opportunities with a close date before March 31, 2022."
-
Prompt 4: "Find all the contacts associated with Lead ID 67890."
-
Prompt 5: "Give me a summary of the contacts and opportunities for Lead ID 54321."
Features and commands
| Feature/Command | Description |
|---|---|
orgAndUsers | This command fetches information about the organization and lists all the users in it. |
groups | This command returns information about the groups in the organization. |
status/{objectType}/ | This command fetches the statuses for leads or opportunities. |
smartViews | This command provides a list of smart views. |
customFields/{cfType}/ | This command retrieves the custom fields for leads, contacts, or opportunities. |
customField/{cfId}/ | This command returns details about a specific custom field, such as choices. |
customActivityTypes | This command provides a list of custom activity types. |
search/{objectType}/ | This command allows you to search for leads, contacts, or opportunities. You need to construct a structured query based on the desired search criteria. |
leadSummary/{leadId}/ | This command returns a detailed summary of a lead, including contacts, emails, phones, and opportunities. It does not include activities. |
leadActivitySummary/{leadId}/activities/ | This command provides a summary of the activities for a lead, such as emails, meetings, tasks, and SMS. You can filter the activities by type or user/group IDs. |
For AI
Nameclose_crm
DescriptionNot all leads are customers, accounts, or potential contacts, always look for matching smart views and lead statuses when unclear terms are used.
`lead` objects may contain multiple `contact`, `opportunity`, `task`, `activity`, and `address` objects. `contact` objects do not have addresses. Activities may have different types, such as `call`, `note`, `meeting`, `sms`, `email`.
Any object contains the following fields: date_created, date_updated, created_by, updated_by.
`lead` objects contain the following fields: name, status_id, url.
`contact` objects contain the following fields: name, title, phone, email, url.
`address` objects contain the following fields: type, address_1, address_2, city, state, zipcode, country. Wrap addresses in a single related `address` query.
`opportunity` objects contain the following fields: status_id, status_type (`active`, `won`, or `lost`), close_date, confidence, value, period, note.
`task` objects contain the following fields: type, assigned_to, is_complete, text, date. Tasks are meant to be completed by sales people and not by leads.
All activities contain the following fields: user_or_group_id, contact_id, type.
`call` activities also contain: call_method, disposition, cost, duration (seconds), direction, local_phone, remote_phone.
`email` activities also contain: status, direction, envelope, subject, body_text, sequence_id, sequence_name.
`meeting` activities also contain: title, location, source, status, attendees, duration, starts_at, ends_at, is_recurring.
`note` activities also contain: note
`sms` activities also contain: status, direction, local_phone, remote_phone, text, attachments.
`custom_activity` contain `custom_activity_type_id`, `status` (`draft` or `published`). To search custom activities, use a `custom_activity` related query and filter by `custom_activity_type_id`, and add any further queries such as a `text` query inside the related query. Custom activities do not include activity types specified above.
All dates in ISO format. Opportunity values in cents.
Search for activity counts on leads using "num_" + plural, e.g. "num_calls", "num_incoming_calls", "num_outgoing_calls" "num_emails", "num_received_emails", "num_sent_emails".
Search for computed fields on leads using "first" or "last" prefix, the object type, and then the field name, e.g. "last_call_created".
To search for leads that haven't been contacted recently, use a negated `related` query with `related_types` set to `call`, `sms`, and `email`. The related query should have a `gt` `date_created` clause and a `field` query with `values` for each user or group ID, if given.
To search for multiple status values, put them all in a single `values` param.
When filtering by multiple users that are part of a group, you must use the group ID inside the search query instead of the user ID.
Search for contact info on leads using "num_email_addresses", "num_phone_numbers" etc.
You must strictly follow the field schema for search queries.
If the user searches for multiple fields related to the same object, you must wrap all the conditions in the same related query, unless the user explicitly states otherwise.
To search for activities, use their type name, such as `call`. Do not search for `activity` directly.
Never use user names, smart view names, status names, or custom field names in queries, always use IDs. Do not alter, prefix, or invent IDs, field names, or field values. Do not add 'custom.' prefix to IDs. Do not use IDs you have not previously seen. Do not expose IDs to the user unless they ask for it.
Always use the info endpoints to fetch IDs for fields or terms not explicitly mentioned in the prompt before performing a search. Always use the info endpoints to fetch information about the org, users, statuses, smart views, and custom fields before performing a search.
To search for `won`, `lost`, or `active` opportunities, use the `status_type` field directly.
If a search returns a `results_url`, you must return it to the user, even if there are no results.
If you receive an error about an invalid ID, refetch the corresponding info endpoint and use the correct ID.
Don't explain the steps you're performing.
When asked to summarize a lead, or create content like drafting an email for a lead, use the leadSummary and leadActivitySummary endpoints, and personalize the content.
Updates
First added7 September 2023