> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Native **Omie** integration vs. contacting Jestor support: when is each one necessary?
- URL: https://blog.jestor.com/native-omie-vs-jestor-support/
- Published: 2026-07-25T03:31:08.000Z
- Updated: 2026-07-25T03:31:08.000Z
- Author: Bruno Bannach

In **[Jestor](https://jestor.com/?ref=blog.jestor.com)**, the native integration with **Omie** is set up in a few minutes with an App Key and App Secret, covering approvals, entries, and orchestration across accounts. Contacting Jestor support, at request@jestor.email, is used for specific low-code setup requests, like connecting a template to **Omie**.

## When to ask the Jestor team for direct help

Companies implementing a ready-made template, like fleet management, or setting up a process from scratch connected to an **ERP**, need to know when the integration already handles it on its own and when it's necessary to ask for technical support.

Without that criterion, the team can waste time trying to manually configure something that requires specific support from Jestor's side.

## How to know which path to follow

1. Set up the native integration directly when connecting your own process to **Omie**.
2. Use the App Key and App Secret, available in **Omie**'s developer panel.
3. Email request@jestor.email when the downloaded template indicates that specific need.
4. Check the documentation attached to the template before trying to configure it manually.
5. Use the native integration as the first option whenever possible, since it's faster.

| Path                                  | How to set it up                                | When to use it                                |
| ------------------------------------- | ----------------------------------------------- | --------------------------------------------- |
| Native **Omie** integration           | App Key and App Secret, directly on the account | Connecting your own process to **Omie**       |
| Jestor support (request@jestor.email) | Direct email contact with the Jestor team       | Templates requiring additional low-code setup |

## Why choose Jestor?

**[Jestor](https://jestor.com/?ref=blog.jestor.com)** charges by users, not by the number of **Omie** accounts connected, so companies with multiple tax IDs or franchises can orchestrate everything with no extra cost per account — contacting support stays reserved for specific, one-off setup cases.

### Frequently Asked Questions

**Does the native Omie integration require technical knowledge?** No, the setup is done with an App Key and App Secret, available in **Omie**'s developer panel.

**Does every template that uses Omie require contacting support?** Not necessarily; some templates explicitly indicate when this additional setup is needed.

**What's Jestor's support email for these cases?** request@jestor.email — it's Jestor's official support email (ticket) channel.

## Reference Video

## Get to know Jestor

With **[Jestor](https://jestor.com/?ref=blog.jestor.com)**, you can automate workflows, connect departments, and build internal systems your way — all without code and with **AI** support.

Get to know [Jestor](https://jestor.com/?ref=blog.jestor.com) at jestor.com and see how to take your company's management to a new level of efficiency and integration.