create_contact
Create and upsert contacts in Propstack CRM by email. Use for leads, web form submissions, or property owners. Get valid source IDs from get_contact_sources.
Instructions
Create a new contact in Propstack CRM.
Use this tool to:
Register a new lead after a phone call
Create a contact from a web form submission
Add a new property owner
Auto-upserts: if a contact with the same email or old_crm_id already exists, it will be updated instead of creating a duplicate.
Use get_contact_sources first to find valid source IDs.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| No | Email address (also used for dedup/upsert matching) | ||
| phone | No | Phone number | |
| rating | No | Contact rating: 0 (none) to 3 (top priority) | |
| company | No | Company name | |
| language | No | Language code (e.g. 'de', 'en') | |
| position | No | Job position/title | |
| broker_id | No | ID of the assigned broker/agent | |
| group_ids | No | Tag/group IDs to assign to this contact | |
| home_city | No | Home address: city | |
| last_name | No | Last name | |
| first_name | No | First name | |
| newsletter | No | Newsletter opt-in | |
| salutation | No | Salutation: mr (Herr) or ms (Frau) | |
| description | No | Free-text description or notes about the contact | |
| home_street | No | Home address: street | |
| office_city | No | Office address: city | |
| home_country | No | Home address: country code | |
| home_zip_code | No | Home address: postal code | |
| office_street | No | Office address: street | |
| academic_title | No | Academic title (e.g. 'Dr.', 'Prof.') | |
| accept_contact | No | Contact permission granted | |
| office_country | No | Office address: country code | |
| office_zip_code | No | Office address: postal code | |
| client_source_id | No | Lead source ID (use get_contact_sources to look up) | |
| client_status_id | No | Contact status ID | |
| home_house_number | No | Home address: house number | |
| office_house_number | No | Office address: house number | |
| partial_custom_fields | No | Custom field values as key-value pairs (use list_custom_fields to discover available fields) |