Add an iFrame integration
When the tool you want isn’t on the marketplace yet, you can embed any web page as a tool dock. Agents press a shortcut and your page loads in a slide-out panel next to the conversation.
Before you start
- A user role that can edit Tool docks settings (typically Admin)
- The address of the page you want to embed (must be reachable over HTTPS)
- If the page requires login: a way for the agent to sign in inside the page
- The page’s
Content-Security-PolicyandX-Frame-Optionsheaders must allow embedding from your Atender domain. If they don’t, the page won’t load — talk to whoever runs the target service.
Steps
- Open Settings → Tool docks.
- Click Add dock and choose Add a web page.
- Enter the page address, including
https://. Atender reads the page’s manifest automatically. If it can’t find one, paste the manifest in when prompted. - If you’re testing a version of the page that isn’t deployed yet, enter its address in the optional Development address field.
- Review what the dock may do. The review lists the permissions and actions the manifest requests, so check that they match what you expect from the page.
- Fill in Name and Letter (agents press
X, then this letter) and pick the Starting width for this dock. If you leave Name empty, the name in the manifest fills it. - Click Add the dock.
- Open any conversation and press
Xthen the dock’s shortcut letter. The dock should slide in with your page loaded.
You can change the name, letter and starting width afterward from the dock’s entry in Settings → Tool docks. See What are Tool Docks? for size guidance.
Verify it worked
- Pressing
X + <your letter>in any conversation opens the dock. - The page loads inside the panel without
Refused to display in a frameerrors in the browser console. - The dock respects the default size set for it.
- If your integration uses Atender’s conversation context, the page reflects the right customer / conversation as soon as it opens.
Troubleshooting
-
Symptom: The dock opens but the page is blank or shows “refused to connect.” Fix: The target page is sending
X-Frame-Options: DENYor aContent-Security-Policy: frame-ancestorsdirective that excludes Atender. The page operator needs to whitelist your Atender domain. There is no client-side workaround. -
Symptom: Atender can’t find a manifest for the page address. Fix: Check that the address is correct and reachable over HTTPS, then paste the manifest in manually when prompted.
-
Symptom: A ClickUp dock can’t be added and the pane says the workspace “cannot store a connection secret yet.” Fix: Web page docks don’t store OAuth credentials, so this only affects ClickUp docks. Your environment is missing the OAuth credential encryption key. Contact your Atender deployment lead — credential encryption requires the key to be configured at the environment level.
-
Symptom: The shortcut conflicts with another tool dock. Fix: Open the conflicting integration and change one of the letters. Only one tool can claim each letter under the
X +namespace. -
Symptom: Agents say “the dock doesn’t know which customer I’m looking at.” Fix: Your integration isn’t reading the conversation context Atender sends. See Tool dock actions reference — the dock has to listen for the context message and update its UI accordingly.