Turn new webinar attendees into Salesforce leads

**Objective:** Create a Salesforce lead for every attendee of the GoTo Webinar webinar `{webinar}` who attended at least `{min-minutes}` minutes (default 0) and is not already a Salesforce contact or lead, with lead source `{lead-source}` (default Webinar).

**Step 1: Find the webinar**

Call `goto-webinar-get-webinar` (GoTo Webinar) with `webinar-name.contains` set to `{webinar}`. If `{webinar}` is all digits, filter by `webinar-key` instead. If more than one webinar matches, list each one's webinar-name, date and webinar-key and stop so the user can choose. If none match, say so and stop. Keep the `webinar-key`, `webinar-name` and `date`.

**Step 2: Read the attendees**

Call `goto-webinar-get-attendee` (GoTo Webinar) with `webinar-key`. Keep attendees whose `total-time-attended` is at least `{min-minutes}` minutes (if total-time-attended comes back in seconds, convert it). Drop rows with a blank email and count them.

**Step 3: Check Salesforce for each attendee**

Match each email address to Salesforce in this order, and stop at the first hit:
1. `salesforce-get-contact` (Salesforce) with `email` set to the address. A hit is a contact: keep `contact-id`, `name`, `account-name`, `account-id` and `owner`.
2. `salesforce-get-lead` (Salesforce) with `email` set to the address. A hit is a lead: keep `lead-id`, `name`, `company`, `status`, `converted` and `owner`. Ignore leads where `converted` is true when a contact also matched.
3. No hit on either: the person is unknown to Salesforce.

Compare addresses case-insensitively and trimmed. Never match on name alone. If one address matches more than one contact, or more than one unconverted lead, mark the person "ambiguous" and list every match rather than picking one.

Only "unknown" attendees go forward. List contacts, leads and ambiguous matches in the report but create nothing for them.

**Step 4: Build the lead list**

`salesforce-add-lead` needs `last-name` and `company`. GoTo Webinar does not return a company, so:
- For a business email domain, propose the domain as the company (jane@acme.com becomes "acme.com").
- For a personal domain (gmail.com, outlook.com, hotmail.com, yahoo.com, icloud.com, aol.com and similar), leave company blank and ask the user for it.
- If last-name is blank, use the part of the email before the @ and flag it.

Show the list as a table: first-name, last-name, email, proposed company, minutes attended. Then STOP and ask the user to confirm, edit the companies, or remove rows. Do not create anything until the user confirms.

**Step 5: Create the leads**

After confirmation, call `salesforce-add-lead` (Salesforce) once per confirmed row with `first-name`, `last-name`, `email`, `company` and `lead-source` set to `{lead-source}` (default Webinar). Do not set `status`, so Salesforce applies its default. If a call fails, record the error and continue with the next row.

**Step 6: Report**

A table of created leads with the returned id, a table of failures with the error, and one line each for how many attendees were already contacts, already leads, ambiguous, skipped for no email, and below the minute threshold.

**Rules & Guidelines:**

* Tools starting goto-webinar- are on the GoTo Webinar server; tools starting salesforce- are on the Salesforce server. Both must be connected.
* The only write this prompt may make is `salesforce-add-lead`, once per confirmed row, after the user confirms in Step 4.
* Do NOT call `salesforce-update-lead`, `salesforce-add-contact`, `salesforce-update-contact` or `salesforce-add-task`. Do NOT call `goto-webinar-add-registrant` or `goto-webinar-delete-registrant`.
* Never create a lead for an email that matched a contact or an unconverted lead.

**Validation:**

* If no attendee qualifies, say so and stop.
* If every attendee is already in Salesforce, report the breakdown and stop without asking for confirmation.
* If two attendee rows share an email, create at most one lead.