about_me
ChatGPTGet a profile of the user who you are working with - including their name, headline, and bio. This is often used when drafting emails to introduce the user to potential clients or new contacts.
add_note
ChatGPTAdd a note to the timeline of a specific person. Because syncKey is not human readable, if you don't already have the key use the person_find tool to find it. If the note is long you should summarize it and put the summary in the subject. If the note is very short, put the entire note in the subject and leave the note field blank. If this tool returns a messageKey, it should not be shared with the user.
add_todo
ChatGPTAdd a to-do to the timeline of a specific person. Because syncKey is not human readable, if you don't already have the key use the person_find tool to find it. If the details are long you should summarize it and put the summary in the subject. If the details are very short, put the entire todo in the subject and leave the details field blank. If this tool returns a messageKey, it should not be shared with the user. If you provide a time without a date, it's assumed to be due today at the time. If you provide no date or time, the to-do is tagged as due "someday" (no specific due date). But, in general, you should encourage users to provide a due date (and optionally time) so that they don't miss getting it done. Don't include a due date in the copy for the subject or details parameters.
canva_create_designs
ChatGPTGenerate designs in Canva that are customized to a specific property or person. For example, this might be posters, social posts, flyers, videos, etc. to market a real estate listing, or materials for onboarding a new employee. This takes brand templates, creates designs from them, and then fills in the details of the property or person into each design (known as "autofill" with "data bindings" in Canva terminology)
full_content
ChatGPTGet the full content of a message or note given a messageKey returned from the timeline tool. The content is formatted as markdown.
person_add
ChatGPTAdd a new person to the user's contact database. Along with the name, you must also submit either an email address or phone number. All other fields are optional (including segment and stage). Leave them blank if you don't know, with 100% certainty, what value to use. If this tool returns a syncKey, it should not be shared with the user but should be retained internally for subsequent API calls that may reference this record. Note that this tool is used only to add people. To add projects you'll need to switch to the project tools.
person_change
ChatGPTMake a set of changes to one or more people. There are two main ways to use this API: (1) If the goal is to change a single person, search for the person using the person_find tool and submit their syncKey in the query parameter along with the changes in the changes parameter. (2) If the goal is to change multiple people, submit a complete search criteria in the query parameter to make changes to multiple people at the same time (a bulk change). In this case you should always first call person_count with your query to see how many people will be affected. If more than one person will be affected, ask the user to explicitly reconfirm (for example, by saying yes) before you call this API to make the actual change. Note that changes are applied asynchronously, so you can let the user know the changes will appear soon. Do not provide a stage, segment, step or category unless the user explicitly asked for one to be added.
person_count
ChatGPTSearch for people and contacts using any of the fields for the record and return the total number of matches.
person_find
ChatGPTSearch for people and contacts using any of the fields for the record and return all matches. Returned syncKey values should not be shared with the user but should be retained internally for subsequent API calls that may reference a record. By default this only returns 10 people. If your goal is to change multiple people, you're better using person_change directly, since you can bulk change all people that match a query. If you want to know what projects this person is a client of, add projects to the projection field.
person_find_steps
ChatGPTSearch for steps based on name, segment, or stage. This is used to find the unique ids of steps to add to other APIs. The input parameters are ANDed together when searching. For each step that matches, the result includes the step id, step name, as well as the segment and stage the step applies to
person_skyslopeforms_brbc
ChatGPTStart Buyer Agreement. A buyer agreement is sometimes referred to as a buyer agency agreement, a buyer representation agreement, a buyer broker agreement, or a BRBC (buyer representation and broker compensation) agreement. This tool starts drafting or writing one of these real estate agreements. This tool may act like a multi-wizard: Based on the inputs, the outputs will tell you whether you need to gather more information from the user and call the tool again.
person_skyslopeforms_file-view
ChatGPTView Form File. This tool lets you view the forms, draft agreements, and signed agreements for the person. This tool may act like a multi-wizard: Based on the inputs, the outputs will tell you whether you need to gather more information from the user and call the tool again.
person_skyslopeforms_listing
ChatGPTStart Listing Agreement. This tool begins drafting or writing a real estate listing agreement (to list a property for sale or rental). This tool may act like a multi-wizard: Based on the inputs, the outputs will tell you whether you need to gather more information from the user and call the tool again.
person_skyslopeforms_offer
ChatGPTWrite an Offer. This tool begins drafting or writing a real estate purchase offer agreement. This tool may act like a multi-wizard: Based on the inputs, the outputs will tell you whether you need to gather more information from the user and call the tool again.
person_tags
ChatGPTReturns the most used tags and lists for people (sorted by most used to least). Note that the words tag and list are used interchangeably.
person_views
ChatGPTReturns the complete set of "audiences" for people. Some users might refer to these as "smart lists" (just the word "list" often refers to what we call "tag"). Internally, the API refers to these as "views". Each item returned includes the view id and name. Use this API to translate from view names to view Ids for other APIs.
project_add
ChatGPTAdd a new project to the user's database. Besides name and address, all other fields are optional (including segment and stage). Leave them blank if you don't know, with 100% certainty, what value to use. If this tool returns a syncKey, it should not be shared with the user but should be retained internally for subsequent API calls that may reference this record. Note that this tool is used only to add projects. To add people you'll need to switch to the people tools.
project_change
ChatGPTMake a set of changes to one or more projects. There are two main ways to use this API: (1) If the goal is to change a single project, search for the project using the project_find tool and submit their syncKey in the query parameter along with the changes in the changes parameter. (2) If the goal is to change multiple projects, submit a complete search criteria in the query parameter to make changes to multiple projects at the same time (a bulk change). In this case you should always first call project_count with your query to see how many projects will be affected. If more than one project will be affected, ask the user to explicitly reconfirm (for example, by saying yes) before you call this API to make the actual change. Note that changes are applied asynchronously, so you can let the user know the changes will appear soon. Do not provide a stage, segment, step or category unless the user explicitly asked for one to be added.
project_count
ChatGPTSearch for projects using any of the fields for the record and return the total number of matches.
project_find
ChatGPTSearch for projects using any of the fields for the record and return all matches. Users don't generally know the term project. Instead they will use words like property, deal, listing, transaction, opportunity or other similar terminology. Often they will use the project segment names as the way to talk about a project. If you're searching by postal address (submitted in the name field), make sure to use a numerical street number not a spelled out street number. Returned syncKey values should not be shared with the user but should be retained internally for subsequent API calls that may reference a record. By default this only returns 10 projects. If your goal is to change multiple projects, you're better using project_change directly, since you can bulk change all projects that match a query. If you need to find the clients of the project (they might be referred to as buyers, sellers, customers, etc.) add clientpeople to the projection field.
project_find_steps
ChatGPTSearch for steps based on name, segment, or stage. This is used to find the unique ids of steps to add to other APIs. The input parameters are ANDed together when searching. For each step that matches, the result includes the step id, step name, as well as the segment and stage the step applies to
project_skyslopeforms_listing
ChatGPTStart Listing Agreement. This tool begins drafting or writing a real estate listing agreement (to list a property for sale or rental). This tool may act like a multi-wizard: Based on the inputs, the outputs will tell you whether you need to gather more information from the user and call the tool again.
project_skyslopeforms_offer
ChatGPTWrite an Offer. This tool begins drafting or writing a real estate purchase offer agreement. This tool may act like a multi-wizard: Based on the inputs, the outputs will tell you whether you need to gather more information from the user and call the tool again.
project_tags
ChatGPTReturns the most used tags and lists for properties (sorted by most used to least). Note that the words tag and list are used interchangeably.
project_views
ChatGPTReturns the complete set of "views" for properties. Some users might refer to these as "smart lists" (just the word "list" often refers to what we call "tag"). Internally, the API refers to these as "views". Each item returned includes the view id and name. Use this API to translate from view names to view Ids for other APIs.
save_draft
ChatGPTSave the draft of an email to Cloze's drafts folder. This will allow the user to edit the email and send it to the recipient. Because syncKey is not human readable, if you don't already have the key use the person_find tool to find it. Never include a greeting or salutation in the body - Cloze will add those separately.
timeline
ChatGPTGet all of the recent communication and notes related to a person. Because syncKey is not human readable, if you don't already have the key use the person_find tool to find it. This gives the context of the relationship with the person. Each item in the list includes a summary of its content. To retrieve the complete details (the full message or note body), you can use the full_content tool.
about_me
Claudeadd_note
Claudeadd_todo
Claudefull_content
Claudeperson_add
Claudeperson_change
Claudeperson_count
Claudeperson_find
Claudeperson_find_steps
Claudeperson_tags
Claudeperson_views
Claudeproject_add
Claudeproject_change
Claudeproject_count
Claudeproject_find
Claudeproject_find_steps
Claudeproject_tags
Claudeproject_views
Claudesave_draft
Claudetimeline
Claude