Follow up with webinar no-shows in Pipedrive

**Objective:** For the webinar named `{webinar-name}`, find the registrants who did not attend and schedule one Pipedrive follow-up activity per no-show who is a Pipedrive person, of type `{activity-type}` (default call) due on `{due-date}` (default the next business day), only after the user confirms.

**Step 1: Find the webinar in GoTo Webinar**

Call `goto-webinar-get-webinar` with `webinar-name.contains` set to `{webinar-name}`. If it matches more than one webinar, list them and stop. If the webinar has not happened yet, say there are no no-shows yet and stop.

**Step 2: Work out the no-shows**

Call `goto-webinar-get-registrant` and `goto-webinar-get-attendee`, both with that `webinar-key`. A no-show is a registrant whose registrant key does not appear among the attendees; fall back to comparing emails case-insensitively when a registrant key is empty.

**Step 3: Match to Pipedrive and avoid duplicates**

Call `pipedrive-get-activity-type` and confirm that `{activity-type}` (or call) is an active activity type key; if it is not, list the available keys and stop. For each no-show, call `pipedrive-get-person` with `email` set to their email. Only an email match counts; list the rest as not in Pipedrive. For each matched person, call `pipedrive-get-activity` with `person-id`, `done` set to false and `subject.contains` set to the webinar name; if an open follow-up already exists, skip that person.

**Step 4: Show the plan and wait**

Show a table: person, organization, owner, email, and the activity you will create (subject `Webinar no-show follow-up: <webinar name>`, type, due date). Ask the user to confirm. Do not write anything until they do.

**Step 5: Write, then confirm**

After confirmation, call `pipedrive-add-activity` once per person with `subject`, `type`, `due-date`, `person-id`, `org-id` when the person has one, and `note` set to `Registered for "<webinar name>" on <registration date> but did not attend. Join link was sent to <email>.` Report each activity as created or failed.

**Rules & Guidelines:**

* `goto-webinar-get-webinar`, `goto-webinar-get-registrant` and `goto-webinar-get-attendee` are on the goto-webinar server; `pipedrive-get-activity-type`, `pipedrive-get-person`, `pipedrive-get-activity` and `pipedrive-add-activity` are on the pipedrive server.
* `pipedrive-add-activity` is the only tool that may write, once per person, and only after confirmation.
* Do not call `pipedrive-update-activity`, `pipedrive-add-note`, `pipedrive-add-person`, `pipedrive-add-lead`, `goto-webinar-add-registrant` or `goto-webinar-delete-registrant`.

**Validation:**

* If every registrant attended, say so and stop.
* If no no-show is in Pipedrive, list them and stop without writing.
* Give the due date as an ISO date; when `{due-date}` is empty, use the next weekday after today.