Agentsia Agents connects your WordPress site to your Agentsia application (app.agentsia.fr). In a few minutes you can:<\/p>\n\n
Three integration methods are available: global settings, shortcodes and Gutenberg blocks.<\/p>\n\n
This plugin is a client for the external Agentsia service and requires an Agentsia account. See the \"External services\" section below for details about the data exchanged.<\/p>\n\n
[agentsia_chatbot]<\/code> \u2014 Full-page chatbot (configurable via attributes).<\/li>\n[agentsia_chatbot mode=\"bubble\"]<\/code> \u2014 Force the floating bubble from a specific page.<\/li>\n[agentsia_chatbot scenario=\"sos\" context_hint=\"AC emergency page\"]<\/code> \u2014 Scenario + page context.<\/li>\n[agentsia_chatbot hide_bubble=\"1\"]<\/code> \u2014 Hide the bubble, open via JavaScript.<\/li>\n[agentsia_booking]<\/code> \u2014 Booking form using the default calendar slug.<\/li>\n[agentsia_booking slug=\"sales-demo\" height=\"780\"]<\/code><\/li>\n[agentsia_demo label=\"Book my demo\"]<\/code> \u2014 Button linking to \/demo<\/code>.<\/li>\n[agentsia_derniers_articles nombre=\"3\" titre=\"Derniers articles\" categorie=\"\" auteur=\"\"]<\/code>: latest published posts of a category (slug or ID) or of an author (ID or login). Without category nor author, on a page: the category whose slug is the page's slug (page \/advisor\/jane-doe\/<\/code> and category jane-doe<\/code>); nothing is shown when there is none.<\/li>\n<\/ul>\n\nGutenberg blocks<\/h4>\n\n\n- Agentsia Chatbot<\/strong><\/li>\n
- Agentsia Booking<\/strong><\/li>\n
- Agentsia Demo button<\/strong><\/li>\n
- Derniers articles<\/strong> (latest posts, same settings as the shortcode)<\/li>\n<\/ul>\n\n
External services<\/h3>\n\n
This plugin is a connector for the Agentsia<\/strong> service (operated by Agentsia, https:\/\/agentsia.fr). It only works with an Agentsia account and communicates with the services described below. By installing and configuring this plugin, you \u2014 and your site visitors \u2014 exchange data with these services.<\/p>\n\n1. Agentsia application \u2014 https:\/\/app.agentsia.fr<\/h4>\n\n\n- From your WordPress server (admin)<\/strong>: when you save the settings and to populate the dropdowns, the plugin calls
https:\/\/app.agentsia.fr\/api\/public\/wp\/me<\/code>, \/api\/public\/wp\/chatbots<\/code> and \/api\/public\/wp\/booking-calendars<\/code>. Data sent: your Agentsia API key (Authorization header) and your site URL (User-Agent header). Data received: your account name, the list of your chatbots and your calendars.<\/li>\n- From your visitors' browser<\/strong>: the chat widget script is loaded from
https:\/\/app.agentsia.fr\/chatbot\/embed.js<\/code>; the appointment booking form is displayed in an iframe https:\/\/app.agentsia.fr\/book\/<slug><\/code>; the \"demo\" button is a plain link to https:\/\/app.agentsia.fr\/demo<\/code>.<\/li>\n<\/ul>\n\n2. Agentsia agent backend \u2014 https:\/\/agent-backend-production-311267441656.europe-west1.run.app<\/h4>\n\n\n- From your visitors' browser<\/strong>: once the chat widget is loaded, the messages typed by your visitors (and the optional page context) are sent to this service to generate the AI agent's replies. No data is sent until a visitor opens and uses the chat.<\/li>\n<\/ul>\n\n
3. One-click connection (\u00ab Connect to Agentsia \u00bb button)<\/h4>\n\n\n- From the administrator's browser<\/strong>: the button opens
https:\/\/app.agentsia.fr\/connect\/wordpress<\/code> with your site address, its REST address and a random one-time value; you log in to Agentsia there and choose a workspace, then come back to your site with a one-time code.<\/li>\n- From your WordPress server<\/strong>: the plugin creates a dedicated user \u00ab Agentsia \u00bb with a limited role (posts, pages, media) and an Application Password for it, then sends to
https:\/\/app.agentsia.fr\/api\/public\/wp\/connect<\/code> the one-time code, your site and REST addresses, a random site identifier, the dedicated user's login and Application Password, and your administrator user ID (default author of articles). Agentsia calls your site back once (\/wp-json\/agentsia\/v1\/environment<\/code>) to check the site holds that password, stores it encrypted, and returns the workspace API key.<\/li>\n- Afterwards<\/strong>, the Agentsia SEO agent uses that dedicated user to read and update your content through the WordPress REST API and the plugin's routes. \u00ab Disconnect \u00bb revokes the Application Password and tells
https:\/\/app.agentsia.fr\/api\/public\/wp\/disconnect<\/code>.<\/li>\n<\/ul>\n\nNo data is transmitted until the plugin has been configured with a valid API key or connected with the button (server side), or the chatbot has been loaded and used (visitor side).<\/p>\n\n
\n- Terms of use: https:\/\/www.agentsia.fr\/conditions-dutilisation\/<\/li>\n
- Privacy policy: https:\/\/www.agentsia.fr\/privacy-policy\/<\/li>\n<\/ul>\n\n
Important (GDPR)<\/strong>: the chatbot sends your visitors' messages to a third-party service. Mention this in your site's privacy policy and, where applicable, obtain the required consent (cookie \/ consent banner).<\/p>\n\n\n\n- Upload the
agentsia-agents<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n- Activate the plugin from the WordPress \"Plugins\" page.<\/li>\n
- Generate an API key in your Agentsia account: My account \u203a API keys \u203a New key<\/strong>. Copy the key (
agsk_\u2026<\/code>) \u2014 it is shown only once.<\/li>\n- Open Settings \u203a Agentsia Agents<\/strong> and paste the key into the \"API key\" field. Save.<\/li>\n
- Select the default chatbot and calendar from the dropdowns (populated automatically from your account).<\/li>\n
- Enable (or not) the global bubble loading, then save again.<\/li>\n
- Use the shortcodes or Gutenberg blocks in your pages.<\/li>\n<\/ol>\n\n\n
\nWhere do I get my API key?<\/h3><\/dt>\nSign in to app.agentsia.fr, then open My account \u203a API keys<\/strong> and click \"New key\". Give it a descriptive name (e.g. \"WordPress site agentsia.fr\"). The full key is shown only once \u2014 copy it into WordPress immediately.<\/p><\/dd>\nWhat if my key is lost or compromised?<\/h3><\/dt>\nFrom My account \u203a API keys<\/strong> on app.agentsia.fr, revoke the existing key and create a new one. Paste the new key into the WordPress plugin. Integrations using the old key will stop working immediately.<\/p><\/dd>\nDoes it work with Divi \/ Elementor \/ Avada?<\/h3><\/dt>\nYes. The shortcodes work in any text module. The Gutenberg blocks work in the native WordPress editor.<\/p><\/dd>\n
Can I disable the chatbot on specific pages?<\/h3><\/dt>\nYes. On the settings page, enter the paths to exclude (one per line).<\/p><\/dd>\n
The chatbot \/ calendar list is empty, why?<\/h3><\/dt>\nMake sure your API key is valid (a \"Connected\" badge appears at the top of the settings page). If it is valid but no chatbot is listed, create one from your Agentsia dashboard. The plugin caches the lists for 5 minutes.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.5.0<\/h4>\n\n\n- New: Custom fields (ACF) in targeted edits<\/strong> \u2014 when ACF is active, the
agentsia\/v1\/content<\/code> route also lists a page's text fields (text, textarea, WYSIWYG) as editable items (f:<name><\/code>, at the end of the list), and the set_field<\/code> operation changes their text in the same request as the other edits. A page with no content of its own, whose text lives in its fields (one page per advisor in a network, for example), can be edited the same way, whether it is built with the block editor, the classic editor or Elementor.<\/li>\n- Contact details and identity are never listed: a field whose name or label refers to a phone, email, address, website, link, social network, photo, logo, name, first name, SIRET, SIREN, RSAC or professional card stays out of Agentsia's reach. Two filters adjust the list on a site:
agentsia_content_excluded_field_patterns<\/code> (excluded words) and agentsia_content_field_units<\/code> (offered fields).<\/li>\n- Rollback:
restore_fields<\/code> puts back the previous value of a field, only for a value Agentsia itself replaced (the last 20 per field).<\/li>\n- New: Latest posts<\/strong> \u2014
[agentsia_derniers_articles]<\/code> shortcode and \u00ab Derniers articles \u00bb block: the latest published posts of a category (categorie<\/code>, slug or ID) or an author (auteur<\/code>, ID or login), 3 by default and 10 at most (nombre<\/code>), with an adjustable heading (titre<\/code>). With neither category nor author, it uses the category that has the same slug as the page (page \/conseiller\/jean-dupont\/<\/code> and category jean-dupont<\/code>); nothing is shown when there is none.<\/li>\n- Fix: targeted edits refused every blog post as a \u00ab shared template \u00bb on themes that have both a PHP
single.php<\/code> and a block index.html<\/code> template. The plugin now picks the same template as WordPress: a theme's PHP template wins over a less specific block template.<\/li>\n<\/ul>\n\n1.4.0<\/h4>\n\n\n- New: One-click connection<\/strong> \u2014 \u00ab Connect to Agentsia \u00bb sends the administrator to log in to Agentsia and pick a workspace; the site is linked without copying any API key or password. A dedicated \u00ab Agentsia \u00bb user is created with a limited role (posts, pages and media only: never users, plugins, themes or settings); \u00ab Disconnect \u00bb revokes its access.<\/li>\n
- New: SEO title, meta description, noindex and canonical URL<\/strong> \u2014 REST route
agentsia\/v1\/seo-meta<\/code> (Application Password, edit_post<\/code> capability) so the Agentsia SEO agent reads and writes them in the active SEO plugin (Yoast SEO, Rank Math, SEOPress, All in One SEO, The SEO Framework), or prints them itself when no SEO plugin is active.<\/li>\n- New: Targeted page edits<\/strong> \u2014 REST route
agentsia\/v1\/content<\/code> lists the sections of a page (blocks, classic content split at its headings, Elementor Heading and Text editor widgets) and changes, adds or removes one without rewriting the page or touching its layout. Refuses Divi\/WPBakery pages. Every write checks the page did not change since it was read.<\/li>\n- New: targeted edits reach the blocks nested in groups, columns and covers (theme patterns): change the words of a paragraph or heading while keeping its style, insert inside a section, duplicate an FAQ question with new texts. Layout blocks and their settings are never modified.<\/li>\n
- New: block themes: the home page, the archive of a post type or a page built in the Site Editor can be edited too (its template, like the Site Editor does; templates shared by several pages are refused).
replace_text<\/code> puts a link on words already in a text (internal linking) without rewriting it.<\/li>\n- New: Structured data (JSON-LD)<\/strong> \u2014 the SEO agent sends an article's JSON-LD through
agentsia\/v1\/seo-meta<\/code> (schema_jsonld<\/code>); the plugin validates it, stores it with the post and prints it in <head><\/code>. It no longer goes into the post content, where WordPress stripped the <script><\/code> tag for the dedicated Agentsia user and showed the JSON as text.<\/li>\n- New: Image alternative text<\/strong> \u2014 REST route
agentsia\/v1\/images<\/code> lists the images of a page and fixes their alt text, both in the media library and in the page content (where the editor copies it). Requires WordPress 6.2+.<\/li>\n<\/ul>\n\n1.3.0<\/h4>\n\n\n- Integration IndexNow et resize des calendriers<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- New: Auto-resize du formulaire de rendez-vous<\/strong> \u2014 l'iframe
[agentsia_booking]<\/code> (shortcode et bloc) ajuste automatiquement sa hauteur au contenu via postMessage (formulaire rempli, questions suppl\u00e9mentaires, calendrier, confirmation). L'attribut height<\/code> ne sert plus que de hauteur initiale \u2014 plus de zone vide ni de scroll interne.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n\n- New: Custom open\/close trigger<\/strong> \u2014 bind any page element (CSS selector) to toggle the chatbot, with automatic grey-out or hide while the assistant is unavailable.<\/li>\n
- New: Default scenario<\/strong> at the global level \u2014 applies a named scenario (defined in the chatbot config on the Agentsia side) on all public pages.<\/li>\n
- New: Hide bubble<\/strong> at the global level \u2014 hides the floating bubble and only opens the chatbot via
window.agentsia.open()<\/code>.<\/li>\n- New: Extended shortcode<\/strong> \u2014
scenario<\/code>, context_hint<\/code>, hide_bubble<\/code> available on [agentsia_chatbot]<\/code>.<\/li>\n- New: Documentation of the JavaScript methods
setWelcomeMessage<\/code>, setQuickReplies<\/code>, setTeaserMessage<\/code>, setAutoOpenDelay<\/code>, setScenario<\/code>, setContext<\/code>, setAppearance<\/code>, apply()<\/code>.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n\n- First public release.<\/li>\n
- Personal API key authentication (generated from app.agentsia.fr).<\/li>\n
- Chatbot and calendar selection via dropdowns (automatic sync from the Agentsia account).<\/li>\n
- Global chatbot (bubble, modal, full-page).<\/li>\n
- Shortcodes and Gutenberg blocks for chatbot, booking and demo button.<\/li>\n
- Complete settings page (API, appearance, exclusions).<\/li>\n<\/ul>","raw_excerpt":"Easily add your Agentsia AI agents (web chatbot, appointment booking, demo funnel) to your WordPress site.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/331696","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=331696"}],"author":[{"embeddable":true,"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/thomasservais"}],"wp:attachment":[{"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=331696"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=331696"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=331696"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=331696"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=331696"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/mfe.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=331696"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}