Webhooks (Integrations)

Webhooks push evaluation data to your other systems — a CRM like Salesforce or Slate, a marketing platform, or a custom endpoint — the moment something happens in TCEvaluator. They’re configured under Admin Settings › Integrations (Manager role and above).

Create an integration

1. Go to Admin Settings › Integrations and click Add Integration.

2. Configure the webhook:

   • Name — a label you’ll recognize, e.g. “Slate — nursing leads”.
   • When to send — the trigger phase:
     • On Submission — fires right after a transcript is submitted. Carries lead/basic data only, so your CRM hears about the prospect immediately.
     • On Completion — fires when the evaluation finishes, with the full results available.
   • Target URL — the HTTPS endpoint on your side that receives the POST.
   • Data To Send — Basic Contact Info, or Complete Evaluation Info (full results; only available with the On Completion phase).
   • Type of record — which sources trigger this webhook (with a Select all option), so you can route website leads and staff-created evaluations to different endpoints.
   • Is Active? — flip off to pause the integration without deleting it.

3. (Optional) Open Advanced Settings to add custom headers (for example an authentication token your endpoint expects) and custom field mapping to reshape the payload to the field names your system wants.

4. Save. The card appears in your integrations list; edit or delete it from the card at any time.

Overlap warning

If another active integration already targets the same URL for the same phase and record type, TCEvaluator warns you — duplicate deliveries are usually a misconfiguration.

Choosing phases: a common setup

Many institutions run two integrations against the same CRM:

1. On Submission → Basic Contact Info — creates the contact/lead record the moment a student uploads.
2. On Completion → Complete Evaluation Info — enriches that record with the credit results when they’re ready.

Endpoint expectations

• Endpoints should accept an HTTPS POST with a JSON body and respond with a 2xx status.
• Use custom headers to carry your endpoint’s auth (API key, bearer token).
• Use custom field mapping when your receiving system requires specific field names — no middleware needed for simple renames.

For delivery into a Student Information System, see SIS integration.