- ThurWiki
- Connectors
Your systems, on the page. Fetched instead of typed out.
A company wiki describes what sits in other systems: customers in the accounts, issues in the ticket system, configurations in the repository. Typed out by hand, it would be wrong the moment the source changed. ThurWiki fetches it from the source and shows it on the page. One click brings it up to date, and every refresh appears in the history.
41 connectors in thirteen groups.
A connector is access to another system, set up in the wiki administration. The macros of that group – the ready-made building blocks for the page – fetch their content through it. The list under each group shows what the connector makes possible in the wiki: macros on the page, or functions such as notifications and the AI assistant. All the connectors are included in the price.
Commercial
The customer with their outstanding invoices on the customer page. The project with its recorded hours on the project page. The ticket in the minutes in which it was discussed.
- Contact (bexio)
- Invoice
- Quotation
- Invoice list
- Project
- Recorded hours
- Customer (WHMCS)
- Services
- Tickets
- Single ticket
- Record (Abacus)
- List
- History
ERP
For anyone whose ERP is not bexio but Odoo or Flectra: the customer with their latest invoices, a single document with its line items, the order or the quotation, an article with price and stock. Flectra is a fork of Odoo and speaks the same interface, hence the same building blocks.
- Customer or supplier
- Invoice (ERP)
- Invoice list (ERP)
- Order or quotation
- Product
Source code
A file from the repository – the store for source code and configurations – with a line range and highlighting on the operations page. Plus the open issues, the latest changes with their author, and the pull requests, that is, proposed changes waiting to be reviewed (Gogs does not have them).
- Issue list (Git)
- Single issue
- File from the repository
- Latest changes
- Pull and merge requests
Ticket systems
A ticket system records enquiries and faults as issues. On the page stand an issue with its status and assignee, the open issues of a project, or the project itself – in the minutes in which they are discussed, for instance.
- Issue
- Issue list
- Project
Jira
The open issues of the project, without opening Jira: as a card, as a list from a Jira search (JQL, Jira's query language) or as a project with its most recently changed issues.
- Issue (Jira)
- Issue list
- Project (Jira)
Software builds
Jenkins builds and tests software automatically, SonarQube examines the source code for faults. On the project page stands whether the last run succeeded and whether the code meets the agreed minimum standards.
- Build status (Jenkins)
- Code quality (SonarQube)
Operations
Zabbix monitors servers and devices, Proxmox VE runs virtual servers. The operations page shows the state of a device, the open problems, the history of a measurement as a chart, and the virtual machines with their state.
- Host status (Zabbix)
- Open problems
- Graph
- VM or container (Proxmox)
- Cluster overview
File storage
File stores that many companies use like a drive on the internet. A text file, or just an extract from it, or the contents of a folder, on the page they belong to.
- File from Nextcloud
- Folder
- File from Seafile
- Folder
CRM
The customer, the contact person, the opportunity and the open case, on the page of the project they belong to, with the notes from the CRM.
- Customer (CRM)
- Person
- Opportunity
- Case
- Notes
Groupware
A contact from the company address book, an appointment, or the week's calendar extract, from Kerio, Nextcloud, Zimbra and other services speaking CalDAV and CardDAV.
- Insert a contact
- Appointment
- Insert appointments
Messaging
An e-mail from the mailbox into the minutes. Notifications about mentions, approvals and watched pages, by whichever route each person chooses.
- Insert an e-mail
- Notification by e-mail
- by Telegram
- by WhatsApp
Artificial intelligence
The assistant beside the page, with the model you choose: a powerful model outside the house for drafting, a model in your own house for confidential company matters. Whisper for voice input and for transcribing voice notes, on your own hardware if you like.
- AI assistant
- Voice input
- Transcripts of voice notes
- Summarising
- Translating
- Building tables
Search and images
Images from Wikimedia Commons, Openverse, Pixabay, Unsplash, Pexels, Freepik, Adobe Stock, Getty Images and iStock, with licence attribution. Web search for the assistant, through SearXNG for instance, a search service you can run yourself. Generating images where the subject does not exist.
- Image search
- Generate an image
- Web search in the assistant
This is how it looks on the page.
Four pages from the demo wiki whose content comes from bexio, Jira and a Git repository. None of it was typed out.
Three principles for the connectors.
Data sources are only read.
The wiki fetches content. It does not write back into bexio, Jira or the CRM. Access therefore needs only the bare minimum of read rights, and a mistake in the wiki can do no harm in bexio. Only the messaging connections (notifications) and the AI connections (your questions to the provider you chose) send anything outwards.
The rights come from the wiki.
Whoever may see a page sees its content, even if they would have no access in the connected system. Whoever uses such a macro therefore decides, by choosing the space, who sees the content. That is intended: the engineer sees the invoice in the minutes without needing a bexio account.
Secrets stay secret.
Access keys and passwords are stored encrypted and, once saved, never shown again, neither in the interface nor through the API. An access belongs either to the wiki or to a person; personal accesses are seen only by the person they belong to.
Setting it up in four steps.
Create access in the source system
An access key, or a user with read rights, in bexio, Jira, Gogs, the CRM or the calendar service. The connector's help text says where.
Enter it in the wiki administration
Administration, Credentials, Add access: choose the kind, enter a label, the address and the key.
Test the connection
A button tests the access and says what it can see: version, number of records, the name of the account. A typing mistake shows up here, not later on a page.
Insert a macro
From now on the macros of that group are ready in the editor. INSERT tab, Macro, Customer (bexio), choose the customer, done.
What companies use the connectors for.
Trades and crafts with bexio
The customer page in the wiki shows the address, outstanding invoices and running projects from bexio. The site report shows the recorded hours. Whoever looks it up in the office brings the state of the accounts across with one click.
IT providers with WHMCS, Git and Zabbix
The customer page shows services and tickets from WHMCS. The operations page shows the configuration from the repository, the open issues from Jira or the ticket system, and the state of the servers from Zabbix and Proxmox. The operations manual fetches its facts instead of having somebody type them out; one click brings them up to date.
Sales and consulting with CRM and Abacus
The project page shows the customer, contact person, opportunity and notes from SuiteCRM or vtiger. From Abacus comes the record with its history: what it looks like today and how it has changed since it was connected.
Questions about the connectors
Which systems can ThurWiki connect to?
41 connectors in thirteen groups: artificial intelligence (Claude through an API key or through signing in at claude.ai, ChatGPT, Google Gemini, DeepSeek, LiteLLM, Ollama, Whisper), search and images (web search, image search across nine archives, image generation), source code (Gogs, GitHub, Bitbucket Cloud, Bitbucket Data Center, GitLab), ticket systems (Mantis, Redmine, Request Tracker, Zammad, YouTrack), Jira (Cloud and Data Center), software builds (Jenkins, SonarQube), operations (Zabbix, Proxmox VE), file storage (Seafile, Nextcloud), commercial systems (bexio, WHMCS, Abacus), ERP (Odoo, Flectra), CRM (SuiteCRM, vtiger), groupware (calendars over CalDAV, address books over CardDAV) and messaging (e-mail mailbox, outgoing mail over SMTP, Telegram, WhatsApp). The connectors are included in the price; AI providers bill their usage through your own key.
Does the wiki write back into the connected systems?
No. Access to the data sources is read-only. The wiki fetches content and displays it; it changes nothing in bexio, Jira or the CRM. Access therefore needs only the bare minimum of read rights. Only two groups send anything outwards: messaging connections send notifications, and AI connections send questions to the provider you chose.
Who sees the content from a connected system?
Whoever may see the wiki page. The rights come from the wiki, not from the source system. Whoever puts an invoice from bexio on a page decides, through the space the page sits in, who sees it.
What does it take to set up a connector?
An account in the source system, usually an access key or a user name and password, and the address of the service. The wiki administrator enters them once in the administration, tests the connection with a button, and after that the access is available to every macro in that group. Secrets are stored encrypted and never shown again.
My system is missing from the list. What now?
Talk to us; we will look at whether and on what terms we can build your source in. We build new connections to the same pattern as the existing ones.
Which source belongs on your pages?
We show you the connectors in a demo wiki, on request with test access to your own bexio, Jira or CRM.