[APP] SetSmart

** Name of app / service **
SetSmart — https://setsmart.io
An AI setter for Instagram, WhatsApp and Messenger DMs: it answers inbound DMs, qualifies leads and books calls on the connected calendar. I work on SetSmart and own the API, so I can provide a test workspace and API key to whoever reviews this.

** Link to developer documentation **
https://setsmart.io/api-documentation

Auth is a single workspace API key sent as an `x-api-key` header (it can also be passed as an `api_key` query parameter or a Bearer token). No OAuth, no expiry, no refresh — so a managed `$auth.api_key` app is all that's needed.

** Is lack of support preventing you from moving forward, or do you have a workaround? **
There is a workaround, but it is a poor one. Users currently reach us from Pipedream through generic HTTP request steps, which means every one of them re-enters the API key in plain text in each step and hand-writes the endpoint paths. Without a registered `setsmart` app slug there is no connected-account experience and the actions are not discoverable in the step picker.

We already maintain first-party integrations elsewhere (Zapier, Make, and an n8n community node), so the API surface is stable and documented, and we are committed to maintaining the Pipedream components long term.

** Are there specific actions or triggers you'd like to see for this app? **
The components are already written and linted against this repo's rules — the branch is ready to open as a PR as soon as the app slug exists:
https://github.com/setsmart-git/pipedream/tree/setsmart-new-components/components/setsmart

14 actions, all verified end-to-end against the live API:

Contacts
- Find Contact — `GET /api/find-contact` (by ID, phone, email, Instagram username or tag)
- Import Contact — `POST /api/import-contact`
- Add Tag To Contact — `POST /api/add-tag-to-conversation`
- Remove Tag From Contact — `POST /api/remove-tag-from-conversation`
- Add Notes To Contact — `POST /api/add-notes`
- Mark Contact As Booked — `POST /api/set-booked`
- Turn AI On — `POST /api/set-ai-on`
- Turn AI Off — `POST /api/set-ai-off`

Leads
- List Leads — `GET /api/leads`
- List Answered Leads — `GET /api/answered`
- List Qualified Leads — `GET /api/ok-call`

Messages
- Send Template Message — `POST /api/send-template` (immediate or scheduled)
- List Scheduled Messages — `GET /api/list-scheduled`
- Cancel Scheduled Message — `POST /api/cancel-scheduled`

Sources would be a natural follow-up (new qualified lead, new booking, lead replied). We publish those events over webhooks today, so an instant source is feasible; happy to add them in a second PR once the actions land.

Happy to provide a sandbox workspace with seeded test data on request.

Review the proposed components in the setsmart-new-components branch, especially components/setsmart, and compare them with this repository's app integration conventions. The immediate scope is registering the setsmart app slug so the existing actions can be submitted as a pull request; done means the app is discoverable and the components are ready for review.

Written by the indexing model from the issue text.