WPForms stores the list ID, tag list, and field mapping inside the form's post_content JSON under providers.aweber. SleekAI maps that JSON into a variable your system message can read, so the bot quotes the real list ID without asking the user to log into AWeber.

Yes. The addon stamps AWeber's response on each entry. If the response code was 201 with a subscriber ID, the bot reports the success. If it was 400 with an error message, the bot quotes that instead of pretending the subscriber synced.

Not if you scope it correctly. Use display conditions to require administrator or editor role, logged-in state, and /wp-admin/ URLs. The widget will not render outside that scope and list IDs and tag rules stay inside the dashboard.

Yes. Conditional rules live inside the same providers.aweber JSON. The bot can describe which conditions fire which connection, so a multi-list form where consultants go to one list and clients go to another stays explainable.

Yes. Multibot mode runs several chatbots on one site. A Lead Magnet bot and a Webinar Signup bot can each have their own prompt and their own scoped data, so the answer is always specific to whichever form a marketer is looking at.

The bot reads what is stored in the WPForms connection JSON. If you added a new custom field in AWeber but did not yet update the form mapping, the bot will accurately say 'this form does not map a value to FIELD_NAME yet' rather than pretending it does.

Yes. Variables resolve at request time, so a change to the AWeber connection JSON shows up in the next answer. There is no need to re-sync the bot when you change a list ID or rename a tag.

You need an account with at least one supported provider. SleekAI works with OpenAI, Anthropic, Google, and OpenRouter, so a cheap fast model can handle list inventory questions while a stronger one runs broader campaign audits. Usage and billing live on your provider account.