Index
What is this integration?
Syltek is an external platform for managing and booking sports courts (padel, tennis and similar). Many clubs use it for their court diary while running the rest of the club —customers, cash, sales— in Golfmanager.
The Syltek Integration module connects the two diaries: when a booking is created or cancelled in one system, the same booking is created or cancelled in the other. That way courts have a single real occupancy, no matter where the booking was taken.
In one sentence: Golfmanager and Syltek remain two separate programs; this integration only makes sure court bookings exist in both at the same time.
What problem does it solve?
Prevents overbooking: a court taken in Syltek is no longer free in Golfmanager, and vice versa.
Removes double entry: nobody has to copy bookings from one diary to the other by hand.
Propagates cancellations: if a booking is cancelled in one system, the slot is released in the other too.
Keeps a record: every sync is logged with how many bookings were downloaded, how many were saved correctly and which ones failed.
Which way does the data travel?
The integration works in both directions, and each direction is switched on separately. You can have one, both, or neither.
From Golfmanager to Syltek: sent immediately
When you save a booking on a linked court, it is created in Syltek straight away.
When the booking is cancelled or deleted, it is cancelled in Syltek too.
Switched on with the "Sincronización de V3 a Syltek" checkbox (sync from V3 to Syltek).
From Syltek to Golfmanager: downloaded every 10 minutes
An automatic process downloads Syltek bookings every 10 minutes.
It brings bookings from today up to one year ahead, and only those that have changed since the previous run.
Switched on with the "Sincronización de Syltek a V3" checkbox (sync from Syltek to V3).
Note: these two checkboxes are currently labelled in Spanish in every language, so you will see them exactly as written above.
⚠️ Cancellations going from Golfmanager to Syltek are always sent as long as the booking has a Syltek ID, even if sending new bookings is switched off. This is deliberate: a booking already created in Syltek must not keep a court occupied after it has been cancelled in Golfmanager.
Prerequisites
Have the Bookings module up and running (the integration works on top of it).
Have the Syltek Integration module installed.
Have the access details provided by Syltek: the system address (host), the API key and the customer the bookings will be created under.
Know the identifier of each court in Syltek, so you can match it with its Golfmanager resource.
Administrator permissions to open Settings and edit resources.
How to set it up (step by step)
A) Connection details
Go to Settings > Bookings > Syltek.
Fill in the Host, the API Key and the Customer ID for bookings that Syltek gave you.
Do not switch on the two sync checkboxes yet: the courts have to be matched first.
B) Match each court
Go to Bookings > Resources and open a court.
Enter in the "ID Syltek" field the identifier that same court has in Syltek.
Save and repeat for every court shared between the two systems.
⚠️ Matching the courts is what decides what gets synced. A booking on a resource without an ID Syltek is not sent, and a booking arriving from Syltek for a court Golfmanager does not recognise is discarded without any warning. If something "is not syncing", start by checking here.
C) (Optional) Match the booking types
Go to Bookings > Booking types and open a type.
Enter its "ID Syltek" if you want the booking to reach Syltek with that specific type.
If you leave it empty, the booking is still created, using Syltek's default type.
D) Switch the sync on
Go back to Settings > Bookings > Syltek.
Tick "Sincronización de V3 a Syltek" to start sending bookings.
Tick "Sincronización de Syltek a V3" to start downloading them. This checkbox turns the automatic 10-minute process on and off.
Wait a few minutes and check the result on the "Syltek sync" screen.
Every field explained
A) Settings > Bookings > Syltek
Field | What it is | What happens if it is missing or wrong |
Host | The address of the club's Syltek system, in the form https://[tenant].syltek.com | Any send or download stops with the message "The Syltek host in the configuration is required". |
API Key | The key that authorises Golfmanager to connect to Syltek. Provided by Syltek. | Message "The Syltek API key in the configuration is required" and no connection is made. |
Customer ID for bookings | The Syltek customer that every booking sent by Golfmanager is created under. | Message "The Syltek client in the configuration is required"; no booking can be sent. |
Resource type id | A field intended to filter by Syltek resource type. It currently has no effect: the module does not use it. | Nothing. It can be left empty. |
Sincronización de V3 a Syltek | Enables sending new Golfmanager bookings to Syltek. | When off, no bookings are created in Syltek (but cancellations are still sent). |
Sincronización de Syltek a V3 | Turns on and off the automatic process that downloads Syltek bookings every 10 minutes. | When off, Golfmanager stops learning about anything booked in Syltek. |
B) Fields the module adds to the records
Field | Where it is | What it is for |
ID Syltek | The resource (court) record | Matches the court with its Syltek counterpart. This is the key field: without it, the court is left out of the sync. |
ID Syltek | The booking type record | Optional. Tells Syltek which reservation type the booking should be created with. |
ID Syltek | The booking record | Informative. The number the booking has in Syltek; filled in by the system. If it is empty, that booking never reached Syltek. |
Syltek original | The booking record | Informative. Marks bookings downloaded from Syltek, as opposed to those born in Golfmanager. |
How it works day to day
A booking created in Golfmanager
When you save it, if the court has an ID Syltek and sending is switched on, it is created in Syltek instantly and the booking stores the number Syltek assigns to it.
What is sent: the name, the start date and time, the duration, the court and, if configured, the booking type.
If the time, duration or court is changed later, Golfmanager cancels the booking in Syltek and creates a new one. It is normal for the Syltek booking number to change.
If anything else is changed (the name, for instance) after it has been sent, that change is not sent again to Syltek.
When it is cancelled or deleted, it is cancelled in Syltek. Syltek does not email the customer about that cancellation.
A booking created in Syltek
It reaches Golfmanager on the next run of the automatic process, at most 10 minutes later.
It is created with the name, court, times and price coming from Syltek, with status Pending.
It has no customer attached: only the name as plain text. If you need to invoice it, assign the customer in Golfmanager.
The price is only copied when the booking has no price; it never overwrites a price already calculated in Golfmanager.
If the time or the court is changed in Syltek, the change is applied in Golfmanager too. If it is cancelled in Syltek, the booking is removed from Golfmanager.
The download is incremental: each run only asks for what has changed since the previous sync, which is why it is fast and does not touch older bookings again.
The "Syltek sync" screen
In the menu you will find the "Syltek sync" entry: the history of syncs, most recent first. It is the first place to look when something does not add up.
Column | What it shows |
Created | When that sync ran. |
Download from | The point in time from which changes were requested from Syltek. |
Downloaded | How many bookings Syltek returned on that run. |
Successfully synced | How many of them were saved correctly in Golfmanager. |
Errors | How many could not be saved. |
Last error | A description of the last failure, including the Syltek booking number affected. |
The "Reset" button
It forces a full download: instead of asking only for recent changes, it fetches every booking from today up to one year ahead.
🚨 Before downloading, "Reset" deletes every future booking marked as "Syltek original" and recreates them from scratch. It is a maintenance operation: use it only if the diary has gone out of step and, preferably, with support on the phone. It also takes several minutes when there are many bookings.
What is NOT synced
Customers. Customer records do not travel between the two systems; from Syltek only the name arrives, as plain text.
Charges, payments and sales. What is charged in Syltek stays in Syltek, and vice versa.
Extras, products and consumptions attached to the booking.
Participants or players on the booking.
Blockings, maintenance, lessons and tournaments that are not a regular court booking.
Prices already calculated in Golfmanager: the Syltek price is only used when the booking has none.
Limitations to keep in mind
One-year window: only bookings between today and one year ahead are downloaded. Anything beyond that does not arrive.
Up to 10 minutes of delay: anything booked in Syltek takes until the next run to appear in Golfmanager. In the other direction the send is immediate.
No matched court means no sync, and the discarded booking raises no warning.
Downloaded bookings arrive as "Pending" and with no customer: they need a manual review if they have to be charged.
Schedule changes are handled by cancelling and recreating in Syltek, so the booking gets a new number there.
It depends on the Syltek service: if Syltek does not respond, that sync fails and is retried on the next run.
Unknown statuses: if a Syltek booking arrives with a status other than "Reservada" (booked) or "Anulada" (cancelled), it is counted as an error and not saved.
Frequently Asked Questions
A booking is not reaching Syltek. What do I check first?
Open the booking and look at the ID Syltek field: if it is empty, it was never sent. The two usual causes are that the court has no ID Syltek or that the "Sincronización de V3 a Syltek" checkbox is off.
There is a booking in Syltek that does not show up in Golfmanager.
Check that the court of that booking is matched in Golfmanager: bookings on unknown courts are discarded. Also check that the "Sincronización de Syltek a V3" checkbox is on and that the "Syltek sync" screen shows recent runs.
How long does a booking made in Syltek take to appear?
At most 10 minutes, which is how often the automatic download runs.
I get an error notification "Syltek error anulando reserva…".
Golfmanager tried to cancel the booking in Syltek and Syltek returned an error or did not respond. The booking is still holding the court in Syltek: cancel it there manually and tell support if it happens again. (The notification text is currently in Spanish in every language.)
I changed the name of a booking and Syltek still shows the old one.
That is the current behaviour: once sent, a booking is only sent again to Syltek when the time, duration or court changes. Other changes are not propagated.
Why do Syltek bookings arrive as "Pending"?
Because they arrive with no customer and no payment: they are court occupancy. If they need invoicing, complete and confirm them in Golfmanager.
Does the customer get an email when a booking is cancelled from Golfmanager?
Not from Syltek: the cancellation is sent explicitly asking for no email to be sent, so the customer does not receive two different messages.
Can I use only one direction of the sync?
Yes. The two checkboxes are independent. Bear in mind that cancellations towards Syltek are sent anyway when the booking already had a Syltek number.
What do I do if the two diaries have gone out of step?
Check the "Syltek sync" history and its Last error column. If the mismatch is widespread, there is the "Reset" button, which deletes future bookings that came from Syltek and downloads them again: do it with support, because it is a destructive operation.
What does the "Resource type id" setting do?
Nothing at the moment. It exists on the settings screen, but the sync does not use it. You can leave it empty.
Recommended best practices
Match every court before switching on the sync checkboxes; that avoids gaps that are hard to spot later.
Decide where each thing gets booked and tell the team: the integration syncs, but it does not resolve two different ways of working.
Check "Syltek sync" during the first weeks, especially the Errors and Last error columns.
Review the "Pending" bookings coming from Syltek if you need to charge them or assign a customer.
Keep the "Reset" button for genuine incidents, with support present.
Whenever a new court is created in either system, remember to fill in its ID Syltek in Golfmanager.