STEP 1
Connect AxisRooms and Djubo
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
AxisRooms and Djubo Integration
Build scheduling workflows between AxisRooms and Djubo on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about AxisRooms and Djubo
Detailed info you need to know about AxisRooms and Djubo integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect AxisRooms to Djubo
Set up your AxisRooms and Djubo integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected AxisRooms and Djubo nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between AxisRooms and Djubo. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between AxisRooms and Djubo work in WEXTL?
WEXTL exposes actions and triggers for AxisRooms and Djubo that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
AxisRooms triggersDjubo actions
AxisRooms modules
- Block Channel InventoryBlocks the inventory for a specified channel to prevent further allocation.
- Enable No Show for BCOMEnables the No Show functionality for BCOM.
- Fetch a PriceFetches a price using the OTA WISE service.
- Fetch InventoryRetrieves the inventory details from the OTA WISE system.
- Get a BookingRetrieves details for a Booking.
- Get Connected OTA by Channel IDRetrieves connected OTA information from Axisrooms using a specified channel ID.
- Make an API CallPerforms an arbitrary authorized API call.
- Unblock Channel InventoryUnblocks channel inventory, allowing previously restricted items to be available for use or sale.
- Update Bulk Inventory in AxisRoomsUpdates bulk Inventory in AxisRooms with new field values.
- Update Bulk PricesUpdates bulk prices in Axisrooms for a specified set of criteria.
- Update InventoryUpdates inventory with new field values.
- Update MLOSUpdates the MLOS in Axisrooms for a particular property or room type.
- Update OTA Credentials by PMS IDUpdates the OTA credentials using a specific PMS ID.
- Update OTA RestrictionsUpdates OTA restrictions such as MLOS, CTA, CTD, and open/close.
- Update Price in AxisRoomsUpdates the price in AxisRooms on a day-wise basis.
- Watch InventoryTriggers when there is an update or change in the inventory.
Djubo modules
- Cancel a BookingCancels an existing booking in the service.
- Get Booking Specific AvailabilityRequests booking-specific availability information.
- Get Booking StatusRetrieves the status of a submitted booking.
- Get Hotel AvailabilityRetrieves hotel availability information for specific dates and preferences.
- Make an API CallPerforms an arbitrary authorized API call.
- Request Expanded AvailabilityRequests expanded availability with detailed information or multiple options.
- Submit a BookingSubmits a booking reservation request to Djubo Direct.
- Sync a BookingSyncs booking changes, such as cancellations or modifications, with Djubo Direct.
Frequently asked questions
Common questions about connecting AxisRooms and Djubo.
Connect your AxisRooms and Djubo accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when AxisRooms's "Watch Inventory" fires, WEXTL can "Cancel a Booking" in Djubo. AxisRooms has 1 trigger (including Watch Inventory); Djubo has 8 actions (including Cancel a Booking, Get Booking Specific Availability, and Get Booking Status). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. AxisRooms-to-Djubo automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment AxisRooms (or Djubo) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your AxisRooms + Djubo automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the AxisRooms and Djubo integration.
- AxisRooms and Djubo integration source code, module specs and credentials implementation.
- Our AxisRooms and Djubo integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AxisRooms and Djubo — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- AxisRooms integration information
- Djubo integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library