Desk-Net can interact with other systems in a variety of ways.
This page provides you with an overview of all integration options:
- Integrating with your Content Management System (CMS) via API
- Content export via ftp
- Importing and exporting events/appointments data
If you have questions about how to integrate with Desk-Net, please email firstname.lastname@example.org.
Integrating with your Content Management System (CMS)
Depending on the CMS you use you have these integration options:
- WordPress Plugin (how it works -- how to set it up -- the plugin on WordPress.org)
- Drupal Module for Drupal7, Drupal8 and Thunder (how it works -- how to set it up -- the module on Drupal.org)
- Other CMS - see description below
Integrating with a CMS other than WordPress or Drupal
You can set up either a one-way or bi-directional integration between your CMS and Desk-Net.
To get an idea of what kinds of use-cases your integration could support, read how our WordPress Plugin works. This documentation can serve as a blueprint for your own integration.
To get and post data to and from Desk-Net, you can use one or both of the following options:
- Desk-Net API: Use our API to send data to Desk-Net or to retrieve it.
- Web-services: Desk-Net contains several web-services for different content management systems.
The web-service sends data to your CMS's REST API.
You can either use that default web-service to send data to your CMS, or you can work with us to have a custom web-service implemented for your CMS if your Desk-Net plan includes this service.
If you are interested in a custom CMS integration, please contact us at email@example.com.
The above-mentioned web-services can export content such as text or picture files that have been uploaded via the Content tab to a REST API.
Instead of using a web-service, you can export such content via ftp in the News ML G2 data standard instead.
Desk-Net handles events and appointments such as press conferences, interview appointments, city hall meetings, or sporting events.
From a structural point of view, events and appointments are the same type of element as a story. The difference is that events and appointments contain an event date (start/end; and optionally an event start and end time).
Reading and exporting events and appointments
Using the Desk-Net API is the best way to read events and appointments. You can get individual appointments by ID or lists of events (e.g. all appointments related to next week's sports pages of your website).
All users can subscribe to a webcal feed using their electronic calendars (e.g. Outlook, iPhone Calendar, etc.). All personal assignments (e.g. attending a press conference) are then exported to the user’s calendar.
The webcal feeds can be found at the bottom of the page Desk-Net > My Settings.
Inserting individual events and appointments
The Desk-Net API allows you to enter new events or appointments, and to edit existing ones.
Desk-Net can import event XML files via ftp from sources such as wire agencies (e.g. dpa, STT, Zapaday) or event databases (e.g. MSU Event, LeoEvent, Tempestiva).
The XML files preferably adhere to the EventsML G2 standard. However, in coordination with the Desk-Net developer team, custom formats can be imported as well.
Inserting and importing event data via an ics file is currently not possible. If this feature is important to you, please contact us at firstname.lastname@example.org to discuss.
Often a story is based on an email that has been received by the newsroom or editorial department.
Importing an email and turning it into a Story is an easy manual process described here.
If you want your team to be able to send emails to Desk-Net to have them automatically converted into calendar events, see "Automatic import into a Calendar".