repairshopr-lead

name	repairshopr-lead
description	Manage leads in RepairShopr CRM - track potential customers
license	MIT
compatibility	opencode
metadata	{"audience":"sales, marketing, technicians","api":"GET /leads, POST /leads, GET /leads/{id}, PUT /leads/{id}"}

What I do

I manage leads in RepairShopr's CRM. Leads represent potential customers who have not yet become full customers. I can list, create, retrieve, and update leads.

When to use me

Use this when:

• Capturing new potential customers from web forms, calls, or walk-ins
• Tracking lead status through sales pipeline (New, Lead, Won, Lost, etc.)
• Updating lead information or converting leads to customers
• Managing lead assignments and follow-ups

How to use

Required API base URL:

• VITE_REPAIRSHOPR_SUBDOMAIN
• VITE_REPAIRSHOPR_API_KEY

Permissions:

• "Leads - List/Search" for listing and viewing single lead
• No special permission required for creating leads
• No special permission required for updating leads

List Leads (GET /leads) Optional filters:

• statuses (array) - Filter by status(es): "New", "Lead", "First Contact", "Opportunity", "Prospect", "Waiting on Client", "In Negotiation", "Pending", "Won", "Lost"
• status_list (string) - Comma-separated statuses
• users (array) - Filter by user IDs
• mailbox_ids (array) - Filter by mailbox IDs
• has_ticket (boolean) - Filter leads with/without tickets
• query (string) - Search query
• page (integer) - Page number (25 results per page)

Create Lead (POST /leads) All fields optional; at minimum you'd provide:

• email, first_name, last_name - Contact info Or
• business_name for company leads

Additional optional fields:

• phone, mobile, address, city, state, zip
• status - Lead status
• user_id - Assigned user
• ticket_description, ticket_problem_type, ticket_subject - For converting to ticket
• ticket_id, customer_id - For linking
• from_check_in (boolean) - Flag for kiosk check-in
• appointment_time, appointment_type_id
• opportunity_start_date, opportunity_amount_dollars, likelihood
• properties, ticket_properties - Custom fields
• And more

Get Lead (GET /leads/{id})

• id (integer) - Lead ID

Update Lead (PUT /leads/{id})

• id (integer) - Lead ID Body fields same as create; all optional

Example call:

// Create a new lead from web form
const lead = await skill({ name: "repairshopr-lead" }, {
  first_name: "John",
  last_name: "Doe",
  email: "[e-mail]",
  phone: "555-1234",
  business_name: "Acme Corp",
  status: "New",
  ticket_description: "Laptop won't boot up, suspects hard drive failure",
  from_check_in: false
})

// Update lead to convert to customer
await skill({ name: "repairshopr-lead" }, {
  status: "Won",
  customer_id: 123  // after creating customer
}, { id: lead.lead.id, method: 'PUT', pathParams: { id: lead.lead.id } })

Response includes:

• Lead object with fields: id, first_name, last_name, email, phone, status, customer_id, ticket_id, user_id, etc.

Important

• Leads can be converted to customers and tickets (via separate operations)
• ticket_description may be required if converting to ticket during creation (validation depends on settings)
• Status values are flexible but follow the typical sales pipeline
• from_check_in indicates kiosk/check-in origin

Related skills

• repairshopr-customer-create - Convert lead to customer
• repairshopr-ticket-create - Convert lead to ticket
• repairshopr-customer-search - For finding existing customers