sevdesk (Edge)

Configure sevdesk as a Source in your Pipeline

Perform the following steps to configure your sevdesk Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select sevdesk.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, sevdesk Source.

   • In the Connect to sevdesk section, specify the following:

     • API Token: The API token that you copied from sevdesk. Enter only the token, without a Bearer prefix.

6. Click Test & Continue to test the connection to your sevdesk Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the entire data of all the selected objects during each Pipeline run, as per the sync frequency.

As sevdesk does not provide a way to fetch only the records that changed, Hevo reads all the records of each object in every run. For the Order Get Discount object, Hevo makes one request for each order, so its ingestion time grows with the number of orders.

You can resync all the objects except the child objects of Order Operation and Receipt Guidance For All Account. When you resync a parent object, Hevo also resyncs its child objects.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

The primary key of most objects is id. The following objects use a different primary key:

• Order Operation: order_id

• Order Get Discount: discount_id

• Receipt Guidance For All Account: receipt_guidance_for_all_account_account_datev_id

• Receipt Guidance Allowed Tax Rule, Receipt Guidance Tax Rate, and Receipt Guidance Allowed Receipt Type: A key that Hevo generates from the parent account and the record.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---