Appearance
Integrations
Taufinity Studio connects to the systems you already run. Every integration lands in the same place: one shared data model and one company brain that your dashboards, your agents and your content pipeline all read from.
There are four families.
| Family | What it does | Pages |
|---|---|---|
| Data sources | Pull history and daily numbers out of shop, marketplace, ads, email and search | 7 |
| Publishing channels | Push finished content out to socials and messaging | 9 |
| Business systems | Read from and write to the tools your team lives in | 7 |
| AI assistants and links | Let assistants, sheets and third parties call Studio safely | 3 |
Data sources
These connectors read your systems and land the result in the Taufinity data warehouse. Nothing is written back, and every connector ships a field allowlist so personal data that has no analytical purpose never lands at all.
| Integration | What it is | What you get |
|---|---|---|
| Shopify | Webshop platform | Orders, refunds, products, inventory, discount codes, landing pages |
| Klaviyo | Email and SMS marketing | Events, metrics, profiles, lists, segments, flows, campaigns |
| Bol.com | Marketplace | Orders, order items, commission, returns, sponsored product performance |
| Google Ads | Paid search and shopping | Daily campaign performance and click level attribution |
| Google Analytics 4 | Web analytics | Daily sessions, engaged sessions and channel grouping as Google defines them |
| Google Search Console | Organic search | Impressions, clicks, position and query per URL per day |
| First-party tracker | Your own site analytics | Pageviews, custom events and consent state, without a third-party script |
Publishing channels
Studio turns one article into channel-native posts and publishes them on approval.
| Integration | Publishing | Notes |
|---|---|---|
| Automatic | Personal profile and company page | |
| Automatic | Feed posts and carousels | |
| Automatic | Page posts, links and polls | |
| Threads | Automatic | Short text, images and carousels |
| Bluesky | Automatic | Short text with link cards |
| Automatic | Pins to a chosen board | |
| TikTok | Automatic | Vertical video from a storyboard |
| Telegram | Automatic | Posts, polls and quiz polls |
| X (Twitter) | Draft only | Studio writes the post, you publish it |
Business systems
| Integration | What it does |
|---|---|
| WordPress | Publish generated articles into an existing WordPress site |
| Odoo | Read and write quotations, orders, contacts and project tasks |
| Google Sheets | Read a sheet as playbook input, write results back |
| Google Drive | Pull documents into the company brain |
| Slack | Spend and failure alerts, plus messages your playbooks post themselves |
| n8n | Trigger an n8n workflow from a playbook step |
| Webhooks | Call any HTTP API, and let any HTTP caller trigger Studio |
AI assistants and links
| Integration | What it does |
|---|---|
| MCP | Connect Claude, Cursor, VS Code Copilot, Gemini CLI or ChatGPT to Studio |
| Share links | Give one tool access to one playbook or dashboard, without an API key |
| Secure embedding | Put a Studio widget inside an authenticated application |
Where the data goes
Every integration in this catalogue runs under the same rules, so you do not have to check them one page at a time.
- EU hosting. Data lands in your own cloud project, in the EU. Nothing is copied to a region you did not choose.
- Least privilege. Read-only credentials where reading is all that is needed. The connectors in the data family hold no permission that could change an order, a price or a customer record.
- Field allowlists. Each data connector declares exactly which fields land. A vendor adding a field does not silently widen what you store.
- Credentials, not configuration. Secrets live in the organisation credential store and are resolved at run time. They never appear in a playbook, a share link or a log line.
- Auditable egress. Every outbound call from a playbook passes an egress policy and is recorded.
Detail: data governance, privacy policy, terms and conditions.
Roadmap and custom integrations
The catalogue above is what is live today, not what is possible.
More integrations are on the roadmap. Marketplaces, ad platforms, CRM and support systems, payment providers, accounting packages, object storage delivery and further social channels are queued. The order they arrive in is driven by what customers ask for, so asking genuinely moves it.
Tools can be requested. If the system you need is not here, tell us what it is and what you want out of it. A connector that one customer needs is usually a connector five customers need. Requests that come with a specific question attached ("we need X so we can answer Y") get built first, because the question is what tells us which fields matter.
You can build your own. Nothing here is a closed set. Three routes, in increasing order of effort:
| Route | Good for | Effort |
|---|---|---|
| Share links | Letting one external tool call one playbook or dashboard, no API key involved | Minutes |
| Webhooks and the API | Any system that speaks HTTP, in either direction, with credentials stored safely | Hours |
| n8n workflows | Visual glue to systems with no connector yet, without writing code | Hours |
Anything the interface can do, the API can do. Sites, playbooks, credentials, content, distributions and reports all have endpoints, so an integration you build yourself is a first-class one rather than a bolt-on.
The point is the combination
A single integration is a report. Two integrations that share an identity graph are an answer.
Klaviyo alone tells you an email campaign got a 41% open rate. Klaviyo joined to Shopify tells you what those opens were worth. Google Ads alone reports its own return on ad spend. Google Ads joined to Shopify orders tells you what the shop actually banked.
See Integration combinations for the recipes that pay for themselves first.