TwitterShots renders public X posts as screenshots and retrieves tweet content and API usage.
Render a public tweet or post and return a provider-hosted temporary URL. Download the result promptly or use Generate Tweet Screenshot when it must be retained. A successful render consumes one API credit.
Render a public tweet or post as an SVG, PNG, or HTML file suitable for saving. A successful render consumes one API credit.
Return the remaining and total TwitterShots API credits for the connected API key. This read does not consume a credit.
Fetch up to 100 public tweets as one Markdown document. Inspect the returned Markdown for a 'Failed to fetch tweets' section because individual IDs can fail within an HTTP 200 response. A successful bulk request consumes one API credit.
Fetch one public tweet as structured Markdown, with optional statistics, media links, and quoted-tweet content. A successful call consumes one API credit.
The TwitterShots integration connects your Dench AI CRM directly to TwitterShots, so agents can read and act on your TwitterShots data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
5 actions are available for agents to invoke on your behalf. Every call runs through TwitterShots's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find TwitterShots and click Connect — you'll authorize access through TwitterShots's own sign-in flow. No API keys or code required.
Ask an agent to use TwitterShots in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench TwitterShots integration connects your AI CRM to TwitterShots, so AI agents can work with your TwitterShots data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The TwitterShots integration currently exposes 5 actions, including Generate Temporary Screenshot URL, Generate Tweet Screenshot, Get API Usage, Get Bulk Tweet Content, and Get Tweet Content. Agents invoke them on your behalf from chat or from automations.
No. You connect TwitterShots from your Dench workspace using TwitterShots's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through TwitterShots's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the TwitterShots connection from your workspace settings at any time.