🇺🇸English

CTC CRM Lead Integration Form

This skill explains how to build and generate robust, modern JavaScript code to integrate a public HTML form with our CTC CRM system.

When generating the code for the user, ALWAYS adhere to the following rules based on the official integration guidelines. Make sure to implement the logic modularly, separating form collection, Turnstile token retrieval, and the fetch request.

1. Authentication and Endpoint

• Endpoint URL : https://api.ctc-crm.com/api/v1/integration/public/leads (Provide staging endpoint only if requested).
• HTTP Method : POST
• Headers : Must send Content-Type: application/json and X-API-Key: YOUR_PUBLIC_API_KEY.
• CRITICAL : The API key MUST be in the X-API-Key header, NOT in the JSON body.
• Remind the user they must replace placeholders with real keys provided by their Project Manager, and ensure their origin domain is allowlisted.

2. Cloudflare Turnstile Verification

• Turnstile is required for public forms. The request body must contain the turnstileToken.
• Implementation : Use invisible Turnstile execution for better UX. Request the token only when the user clicks submit.
• Render the widget into a hidden slot, grab the token upon execution, and send it with the request.

3. Payload Schema Requirements

• Required Fields :
  • name (string)
  • email (string, must be validated on the client)
  • turnstileToken (string, generated dynamically before submit)
• Optional Fields :
  • phone (string)
  • companyName (string)
  • address (string)
  • externalId (string)
  • message (string)
  • interestedIn (string array): Convert user's comma-separated input into a clean string array.

4. Normalization and Duplicate Prevention

• Implement duplicate prevention: disable the submit button and show a "Sending..." state during the request.
• Ensure the email is converted to lowercase on the client side.
• Filter out empty optional strings when building the payload.

5. Success and Error Handling

• Handle errors using HTTP status codes.
• 400: Bad request
• 403: Origin not allowlisted or Turnstile error
• 429: Too many requests/Duplicate submission
• Do not expose exact error messages to the user. Show generic messages like "Your request could not be submitted. Please try again."
• Make sure to clear the Turnstile token and reset the Turnstile widget on both success and error.

6. Output Generation Strategy

When tasked with generating an integration script, provide the HTML structure for the form (input fields matching the schema) and the vanilla JS needed to collect the values, acquire the Turnstile token, and make the API request. Explain the key configurations at the top of your response.

Weekly Installs

1

Repository

comparethecarri…t-skills

First Seen

1 day ago

Security Audits

Gen Agent Trust HubPassSocketPassSnykWarn

Installed on

windsurf1

amp1

cline1

trae1

opencode1

cursor1