35CRM Sales Lead Management

Problem

When wiring 35CRM sales lead endpoints into an agent workflow, the brittle parts are often auth, encoding, and response shape rather than the business fields themselves. crm-saleslead-mgmt targets that integration surface for basic sales lead operations, including lead list queries, lead creation, and follow-up list queries, while keeping Token auth, Chinese request encoding, date format, and rows / data parsing consistent.

How It Works

The skill starts by collecting the required credentials, then validates the token with crm_login.py, returning success, token, and base_url. Credentials are reused within the session instead of being re-asked. Subsequent calls normally go through crm_query.py or crm_form_submit.py rather than raw curl.
- Query: POST /salesLead/list, POST /SalesLeadFollow/list.
- Create: use viewId=SalesLeadAdd in the generic form flow: fetch view/form, parse fields, then submit insert.
- Runtime constraints: Chinese payloads should go through Python scripts; multipart can be sent with curl --data-binary @- via subprocess; dates use Y-m-d H:i:s; response parsing prefers resp.get('rows') or resp.get('data') or [].

Boundaries

This fits teams that already expose 35CRM lead endpoints and need reliable reads or writes for sales leads and follow-ups. It does not replace CRM configuration, permission design, or data cleaning, and it should not assume every field is returned by generic queries. If the API shape changes, check authentication.md, base.md, enums.md, sales_lead.md, and sales_lead_follow.md for field and enum definitions.