Wiresk

Wiresk

Odoo – Connection & Settings

Estimated reading time: 11 min
Odoo banner

Odoo is a powerful business management platform, and it can be even more powerful when integrated with other applications. This allows you to automate tasks, streamline your workflows, and get a more complete view of your business.

Wiresk makes it easy to connect Odoo to any application that has an API, including CRM systems, marketing automation platforms, and accounting software.

Connect Odoo to Wiresk Copy Link

There are two ways to connect your app to Wiresk:

  • In “My apps” section, where you can manage your connections (select or create your group first to get access to this section, refer to the Group system ).
  • While building your Flow, you can easily establish a connection to your app directly within the Flow builder. This can be done during the setup of either a Trigger or a Method.

This guide explains how to set up a connection in “My apps” section, which is essentially the same process as creating one on-the-go.

  • On your Wiresk’s Dashboard, select your Group.
  • On the left panel, go to “My apps” and select Screenshot 2025 04 08 at 9.58.41 in the morning Odoo - Connection & Settings
  • Search the app name in the search field or select it in the apps list.
Animated image GIF, showing the step of how to create an app connection. First, select the group then select My Apps tab, and click on the "+ create" button.

On the connection settings panel:

  • Give a name to your connection
  • Enter your Odoo Instance URL
    • (For example, the link of your Odoo domaine is https://wiresk.odoo.com/odoo, your Instance URL is https://wiresk.odoo.com)
  • Enter your Odoo Database Name, this name is also in your Odoo Instance URL, for example, https://wiresk.odoo.com, wiresk is your Database name
  • Enter the Odoo Username (User’s credentials from the Database)
  • Enter the Odoo Password linked to your username
  • Click on “Create App” button, voila! Your Odoo app is now created in Wiresk.
Odoo connection setup form in Wiresk. The form includes required fields for Name, Odoo Instance URL, Odoo Database Name, Odoo Username, and Odoo Password. At the bottom are two buttons: “Test” on the left and “Create” on the right.

You can now use this Connection to create your Flows with Odoo.

Now that your app is linked to Wiresk, you’re ready to start building Flows.

Simple steps to create a Flow ↓
  • Select your Group, then on the Flow management screen click on “Create Flow”.
  • On the new screen, name the new Flow.
GIF animated screen of Wiresk, showing the way to create a new Flow.

Add a Trigger that will start your Flow

Flows can be executed by multiple Triggers, depending on the desired workflow. For example, you could use scheduled Triggers with different recurrence rules alongside a Webhook Trigger for immediate, event-driven runs of the Flow. If you choose to “Run Once“, the Flow will execute using only one Trigger and its sample data.
  • Click on the (+) button to open the Trigger settings side panel.
  • On the settings side panel, click on the “+ Add” button.
Screenshot of the Wiresk side panel titled “Trigger.” The panel shows a section labeled “All Triggers” with a blue “+ Add” button for inserting a new Trigger.
  • On the Trigger selection screen, search your app or select it from the list below the screen.
Screenshot of Wiresk Trigger setting screen. Red arrows shows that you can wether search your app in the search or or select it in the list below.
  • Select your preferred Trigger on the next screen and customize its settings.
As mentioned in “How to connect your app to Wiresk” above, during your Trigger settings, you can create a new connection to your apps at this stage.

Add a Method that will execute a task

The Method will perform a specific task on a particular app or service you’ve connected to Wiresk like get info or send emails.

You can add at least 1 or multiple Methods for complex Flows (a maximum of 255 Methods).
  • On the Flow builder, select the (+) plus button next the Trigger button.
  • Search or scroll down to select the app that will perform a task.
  • Configure the Methods settings, refer to it documentation in our Help Center.
Screenshot of Wiresk Flow Builder with a Flow named “Flow Example.” The canvas shows a Gmail Trigger on the left connected to an empty step placeholder marked with a plus icon in the center. On the right, the panel lists available apps and tools. A search bar is displayed at the top of the panel for filtering apps. Red arrows highlight the empty step placeholder, the search bar, and items in the app list.

Add Wiresk Tools to your Flow

If you want to build a complex Flow, Wiresk offers a selection of tools at your disposal. Refer to Wiresk’s Tools

To add Tools in your Flow, Follow the same step as adding the Methods.

  • On the Flow builder screen, click on the plus button (+) then just click on the “Tool” tab and select the Tool that you want to add.
Screenshot of Wiresk Flow Builder showing a Gmail Trigger connected to an empty Method placeholder. A red arrow points to the empty step circle with a plus sign where the next action will be added. On the right side, the “Tool” tab is selected in the panel. Another red arrow highlights the “Tool” tab label at the top. A search bar is shown above a list of available tools.
You can refer to “How to Create a Flow” tutorial for more detailed instructions, including step-by-step guidance on mapping and configuration.

What will start your automation…

Run Once Tab: This tab allows you to schedule a Flow to execute a single time at a specific date and time. This is ideal for one-time operations such as data syncs, cleanups, or initial configuration steps. After execution, the schedule will be automatically cleared unless rescheduled manually.

Run Tab: This tab is used to set up repeating schedules:

  • Repeat feature: This dropdown determines how long the automation will continue repeating based on the selected frequency (Minutely or Hourly). You can choose from:
    • Repeat Forever
      • The automation will continue to run indefinitely at the defined interval (e.g. every 15 minutes).
      • No end condition is specified.
    • Repeat for (x) Times
      • You set a specific number of repetitions.
      • Requires the field Number (x) of Repeat Times to be filled (e.g. 10 times).
    • Repeat Between Start & End Dates
      • The automation will run only within a defined date range.
      • Additional fields will appear to select start and end dates.
      • Useful for limited-time schedules like campaigns or batch jobs.
  • Daily at Multiple Times: Sets the Flow to run several times per day based on a minutely or hourly interval.
  • Daily: This allows a Flow to run x times per day at a specific time.
  • Weekly: This allows you to run a Flow weekly by selecting the days and time.
  • Monthly: This will monitor your Trigger every month on a defined date and hour.
  • Yearly: This will monitor your Trigger on a specific date and hour every year.
  • Specific dates: This will start your Trigger on specific dates and time.

For more details, see Wiresk Scheduler – The Fundamentals.

After configuring your Trigger, you can load sample data into the Example Input panel in Flow Builder. This gives you a preview of what the Trigger returns and prepares the data for mapping.

How to get it:

  • Enter manually: Add your own sample data in the JSON editor, plain JSON string, or form view.
  • Use predefined Trigger samples: Triggers provide ready-made sample data that can be pulled directly into the Example Input panel.
  • Capture Example Input: Enable this option to record real data the next time the Flow runs. The captured sample will automatically appear in the panel.

With Sample Input in place, you can review the field structure and connect Trigger outputs to Method parameters with confidence.

For more details, refer to Example Input – How it Works.

Run your Flow at a Specific time or intervals automatically instead of being triggered manually or by events like Webhooks.

Retrieve multiple records from Odoo Database using Wiresk’s Query Builder.
A Query Builder allows you to create complex SQL queries without having to write any code.
This allows non-technical users to easily access and analyze data with a graphical user interface.
✓ When This Trigger is activated, the result of the Query can be use to Map your Methods.

Configuration Table:

Name*Retrieve Records using Wiresk’s Query Builder
Connection*Select your connection or create one Refer to how to create a connection.
Time outYou can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage.
Recurrence rule/scheduler*Set up your recurrence rule
Parameters
Entity* (Set of data that contain records)Select the Entity where the data records are located.
For example, “Calendar event“, “Email Thread“, or “Companies“.
Configure FilterThis tab enables you to define specific criteria to narrow down the records being retrieved.
Configure Columns

Preview Data



Number of records:10

Begin at record:0

Edit Columns


Configure Sorting		Configure which columns or fields of data will be retrieved and included in the output.

To visualize the records. You must select at least 1 Columns to get the Preview Data.
If you get this message:” Cannot convert undefined or null to object”, it means there is no records.

By default, 10 records will be shown.

The display starts at record 0.

Customize which columns are displayed and retrieved. Minimum 1 column, maximum 50 columns.

This option is for sorting the data in the columns by Ascending or descending order.

(*) required field

What your automation will do…

Below is a list of Entities (Records) that you can interact with, in Wiresk Methods.

Model in Odoo(Entity) Model (Entity in Wiresk) Description Type Transient Model 
extract.mixin Base class to extract data from documents Base Object FALSE 
calendar.event Calendar Event Base Object FALSE 
res.partner Contact Base Object FALSE 
discuss.channel Discussion Channel Base Object FALSE 
mail.thread.cc Email CC management Base Object FALSE 
mail.thread Email Thread Base Object FALSE 
iap.account IAP Account Base Object FALSE 
crm.lead Lead/Opportunity Base Object FALSE 
mail.blacklist Mail Blacklist Base Object FALSE 
mail.thread.blacklist Mail Blacklist mixin Base Object FALSE 
mail.thread.main.attachment Mail Main Attachment management Base Object FALSE 
phone.blacklist Phone Blacklist Base Object FALSE 
mail.thread.phone Phone Blacklist Mixin Base Object FALSE 
crm.team Sales Team Base Object FALSE 
crm.team.member Sales Team Member Base Object FALSE 
spreadsheet.cell.thread Spreadsheet discussion thread Base Object FALSE 
auth_totp.wizard 2-Factor Setup Wizard Base Object TRUE 
res.users.apikeys.description API Key Description Base Object TRUE 
res.groups Access Groups Base Object FALSE 
ir.actions.act_url Action URL Base Object FALSE 
ir.actions.act_window Action Window Base Object FALSE 
ir.actions.act_window_close Action Window Close Base Object FALSE 
ir.actions.act_window.view Action Window View Base Object FALSE 
ir.actions.actions Actions Base Object FALSE 
mail.activity Activity Base Object FALSE 
mail.activity.mixin Activity Mixin Base Object FALSE 
mail.activity.plan Activity Plan Base Object FALSE 
mail.activity.type Activity Type Base Object FALSE 
mail.activity.plan.template Activity plan template Base Object FALSE 
mail.activity.schedule Activity schedule plan Wizard Base Object TRUE 
format.address.mixin Address Format Base Object FALSE 
ir.profile Allow profiling only to Tech Support level Base Object FALSE 
ir.module.category Application Base Object FALSE 
ir.asset Asset Base Object FALSE 
web_editor.assets Assets Utils Base Object FALSE 
ir.attachment Attachment Base Object FALSE 
auth_totp.device Authentication Device Base Object FALSE 
ir.autovacuum Automatic Vacuum Base Object FALSE 
avatar.mixin Avatar Mixin Base Object FALSE 
res.bank Bank Base Object FALSE 
res.partner.bank Bank Accounts Base Object FALSE 
base Base Base Object FALSE 
base_import.import Base Import Base Object TRUE 
base_import.mapping Base Import Mapping Base Object FALSE 
crm.activity.report CRM Activity Analysis Base Object FALSE 
crm.iap.lead.industry CRM IAP Lead Industry Base Object FALSE 
crm.iap.lead.mining.request CRM Lead Mining Request Base Object FALSE 
crm.recurring.plan CRM Recurring revenue plans Base Object FALSE 
crm.stage CRM Stages Base Object FALSE 
crm.tag CRM Tag Base Object FALSE 
calendar.attendee Calendar Attendee Information Base Object FALSE 
calendar.filters Calendar Filters Base Object FALSE 
calendar.popover.delete.wizard Calendar Popover Delete Wizard Base Object TRUE 
calendar.provider.config Calendar Provider Configuration Wizard Base Object TRUE 
utm.stage Campaign Stage Base Object FALSE 
bus.listener.mixin Can send messages via bus.bus Base Object FALSE 
mail.canned.response Canned Response Base Object FALSE 
change.password.wizard Change Password Wizard Base Object TRUE 
discuss.channel.member Channel Member Base Object FALSE 
ir.actions.client Client Action Base Object FALSE 
spreadsheet.revision Collaborative spreadsheet revision Base Object FALSE 
bus.bus Communication Bus Base Object FALSE 
res.company Companies Base Object FALSE 
base.document.layout Company Document Layout Base Object TRUE 
res.config Config Base Object TRUE 
res.config.settings Config Settings Base Object TRUE 
ir.actions.todo Configuration Wizards Base Object FALSE 
crm.lead2opportunity.partner.mass Convert Lead to Opportunity (in mass) Base Object TRUE 
crm.lead2opportunity.partner Convert Lead to Opportunity (not in mass) Base Object TRUE 
spreadsheet.dashboard.share Copy of a shared dashboard Base Object FALSE 
res.country Country Base Object FALSE 
res.country.group Country Group Base Object FALSE 
format.vat.label.mixin Country Specific VAT Label Base Object FALSE 
res.country.state Country state Base Object FALSE 
wizard.ir.model.menu.create Create Menu Wizard Base Object TRUE 
res.currency Currency Base Object FALSE 
res.currency.rate Currency Rate Base Object FALSE 
ir.ui.view.custom Custom View Base Object FALSE 
decimal.precision Decimal Precision Base Object FALSE 
ir.default Default Values Base Object FALSE 
ir.demo Demo Base Object TRUE 
ir.demo_failure.wizard Demo Failure wizard Base Object TRUE 
ir.demo_failure Demo failure Base Object TRUE 
res.device.log Device Log Base Object FALSE 
res.device Devices Base Object FALSE 
digest.digest Digest Base Object FALSE 
digest.tip Digest Tips Base Object FALSE 
mail.followers Document Followers Base Object FALSE 
mail.alias Email Aliases Base Object FALSE 
mail.alias.mixin Email Aliases Mixin Base Object FALSE 
mail.alias.mixin.optional Email Aliases Mixin (light) Base Object FALSE 
mail.alias.domain Email Domain Base Object FALSE 
mail.template.preview Email Template Preview Base Object TRUE 
mail.template Email Templates Base Object FALSE 
mail.compose.message Email composition wizard Base Object TRUE 
mail.resend.message Email resend wizard Base Object TRUE 
ir.embedded.actions Embedded Actions Base Object FALSE 
base.enable.profiling.wizard Enable profiling for some time Base Object TRUE 
calendar.alarm Event Alarm Base Object FALSE 
calendar.alarm_manager Event Alarm Manager Base Object FALSE 
calendar.event.type Event Meeting Type Base Object FALSE 
calendar.recurrence Event Recurrence Rule Base Object FALSE 
ir.exports Exports Base Object FALSE 
ir.exports.line Exports Line Base Object FALSE 
html.field.history.mixin Field html History Base Object FALSE 
ir.model.fields Fields Base Object FALSE 
ir.fields.converter Fields Converter Base Object FALSE 
ir.model.fields.selection Fields Selection Base Object FALSE 
crm.lead.scoring.frequency.field Fields that can be used for predictive lead scoring computation Base Object FALSE 
ir.binary File streaming helper model for controllers Base Object FALSE 
ir.filters Filters Base Object FALSE 
snailmail.letter.format.error Format Error Sending a Snailmail Letter Base Object TRUE 
crm.lead.lost Get Lost Reason Base Object TRUE 
google.gmail.mixin Google Gmail Mixin Base Object FALSE 
portal.wizard Grant Portal Access Base Object TRUE 
spreadsheet.dashboard.group Group of dashboards Base Object FALSE 
mail.guest Guest Base Object FALSE 
ir.http HTTP Routing Base Object FALSE 
crm.iap.lead.helpers Helper methods for crm_iap_mine modules Base Object FALSE 
iap.enrich.api IAP Lead Enrichment API Base Object FALSE 
iap.autocomplete.api IAP Partner Autocomplete API Base Object FALSE 
iap.service IAP Service Base Object FALSE 
mail.ice.server ICE server Base Object FALSE 
image.mixin Image Mixin Base Object FALSE 
base.import.module Import Module Base Object TRUE 
fetchmail.server Incoming Mail Server Base Object FALSE 
res.partner.industry Industry Base Object FALSE 
base.language.install Install Language Base Object TRUE 
mail.wizard.invite Invite wizard Base Object TRUE 
base.language.export Language Export Base Object TRUE 
base.language.import Language Import Base Object TRUE 
res.lang Languages Base Object FALSE 
crm.lead.scoring.frequency Lead Scoring Frequency Base Object FALSE 
sms.tracker Link SMS to mailing/sms tracking models Base Object FALSE 
ir.logging Logging Base Object FALSE 
mail.bot Mail Bot Base Object FALSE 
mail.composer.mixin Mail Composer Mixin Base Object FALSE 
mail.gateway.allowed Mail Gateway Allowed Base Object FALSE 
discuss.channel.rtc.session Mail RTC session Base Object FALSE 
mail.render.mixin Mail Render Mixin Base Object FALSE 
ir.mail_server Mail Server Base Object FALSE 
mail.template.reset Mail Template Reset Base Object TRUE 
mail.tracking.value Mail Tracking Value Base Object FALSE 
ir.ui.menu Menu Base Object FALSE 
crm.merge.opportunity Merge Opportunities Base Object TRUE 
base.partner.merge.line Merge Partner Line Base Object TRUE 
base.partner.merge.automatic.wizard Merge Partner Wizard Base Object TRUE 
mail.message Message Base Object FALSE 
mail.notification Message Notifications Base Object FALSE 
mail.message.reaction Message Reaction Base Object FALSE 
mail.message.translation Message Translation Base Object FALSE 
mail.message.subtype Message subtypes Base Object FALSE 
discuss.voice.metadata Metadata for voice attachments Base Object FALSE 
mail.tracking.duration.mixin Mixin to compute the time a record has spent in each value a many2one field can take Base Object FALSE 
ir.model.access Model Access Base Object FALSE 
ir.model.constraint Model Constraint Base Object FALSE 
ir.model.data Model Data Base Object FALSE 
ir.model.inherit Model Inheritance Tree Base Object FALSE 
ir.model Models Base Object FALSE 
ir.module.module Module Base Object FALSE 
base.module.install.request Module Activation Request Base Object TRUE 
base.module.install.review Module Activation Review Base Object TRUE 
report.base.report_irmodulereference Module Reference Report (base) Base Object FALSE 
base.module.uninstall Module Uninstall Base Object TRUE 
ir.module.module.dependency Module dependency Base Object FALSE 
ir.module.module.exclusion Module exclusion Base Object FALSE 
crm.lost.reason Opp. Lost Reason Base Object FALSE 
mail.mail Outgoing Mails Base Object FALSE 
sms.sms Outgoing SMS Base Object FALSE 
report.paperformat Paper Format Config Base Object FALSE 
res.partner.autocomplete.sync Partner Autocomplete Sync Base Object FALSE 
res.partner.category Partner Tags Base Object FALSE 
res.partner.title Partner Title Base Object FALSE 
mail.resend.partner Partner with additional information for mail resend Base Object TRUE 
res.users.identitycheck Password Check Wizard Base Object TRUE 
crm.iap.lead.role People Role Base Object FALSE 
crm.iap.lead.seniority People Seniority Base Object FALSE 
portal.mixin Portal Mixin Base Object FALSE 
portal.share Portal Sharing Base Object TRUE 
portal.wizard.user Portal User Config Base Object TRUE 
privacy.log Privacy Log Base Object FALSE 
privacy.lookup.wizard Privacy Lookup Wizard Base Object TRUE 
privacy.lookup.wizard.line Privacy Lookup Wizard Line Base Object TRUE 
ir.cron.progress Progress of Scheduled Actions Base Object FALSE 
publisher_warranty.contract Publisher Warranty Contract Base Object FALSE 
mail.push.device Push Notification Device Base Object FALSE 
mail.push Push Notifications Base Object FALSE 
ir.qweb.field.time QWeb Field Time Base Object FALSE 
ir.qweb Qweb Base Object FALSE 
ir.qweb.field Qweb Field Base Object FALSE 
ir.qweb.field.barcode Qweb Field Barcode Base Object FALSE 
ir.qweb.field.contact Qweb Field Contact Base Object FALSE 
ir.qweb.field.date Qweb Field Date Base Object FALSE 
ir.qweb.field.datetime Qweb Field Datetime Base Object FALSE 
ir.qweb.field.duration Qweb Field Duration Base Object FALSE 
ir.qweb.field.float Qweb Field Float Base Object FALSE 
ir.qweb.field.float_time Qweb Field Float Time Base Object FALSE 
ir.qweb.field.html Qweb Field HTML Base Object FALSE 
ir.qweb.field.image Qweb Field Image Base Object FALSE 
ir.qweb.field.image_url Qweb Field Image Base Object FALSE 
ir.qweb.field.integer Qweb Field Integer Base Object FALSE 
ir.qweb.field.many2one Qweb Field Many to One Base Object FALSE 
ir.qweb.field.monetary Qweb Field Monetary Base Object FALSE 
ir.qweb.field.relative Qweb Field Relative Base Object FALSE 
ir.qweb.field.selection Qweb Field Selection Base Object FALSE 
ir.qweb.field.text Qweb Field Text Base Object FALSE 
ir.qweb.field.qweb Qweb Field qweb Base Object FALSE 
ir.qweb.field.many2many Qweb field many2many Base Object FALSE 
ir.rule Record Rule Base Object FALSE 
ir.model.relation Relation Model Base Object FALSE 
mail.blacklist.remove Remove email from blacklist wizard Base Object TRUE 
phone.blacklist.remove Remove phone from blacklist Base Object TRUE 
ir.actions.report Report Action Base Object FALSE 
report.layout Report Layout Base Object FALSE 
sms.resend.recipient Resend Notification Base Object TRUE 
reset.view.arch.wizard Reset View Architecture Wizard Base Object TRUE 
resource.mixin Resource Mixin Base Object FALSE 
resource.calendar.leaves Resource Time Off Detail Base Object FALSE 
resource.calendar Resource Working Time Base Object FALSE 
resource.resource Resources Base Object FALSE 
sms.account.phone SMS Account Registration Phone Number Wizard Base Object TRUE 
sms.account.sender SMS Account Sender Name Wizard Base Object TRUE 
sms.account.code SMS Account Verification Code Wizard Base Object TRUE 
sms.resend SMS Resend Base Object TRUE 
sms.template.preview SMS Template Preview Base Object TRUE 
sms.template.reset SMS Template Reset Base Object TRUE 
sms.template SMS Templates Base Object FALSE 
discuss.gif.favorite Save favorite GIF from Tenor API Base Object FALSE 
ir.cron Scheduled Actions Base Object FALSE 
mail.scheduled.message Scheduled Message Base Object FALSE 
mail.message.schedule Scheduled Messages Base Object FALSE 
sms.composer Send SMS Wizard Base Object TRUE 
ir.sequence Sequence Base Object FALSE 
ir.sequence.date_range Sequence Date Range Base Object FALSE 
ir.actions.server Server Action Base Object FALSE 
ir.min.cron.mixin Set Min Next call on metabase Base Object FALSE 
res.users.apikeys.show Show API Key Base Object FALSE 
snailmail.letter Snailmail Letter Base Object FALSE 
spreadsheet.dashboard Spreadsheet Dashboard Base Object FALSE 
spreadsheet.mixin Spreadsheet mixin Base Object FALSE 
mail.link.preview Store link preview data Base Object FALSE 
ir.config_parameter System Parameter Base Object FALSE 
template.reset.mixin Template Reset Mixin Base Object FALSE 
web_tour.tour.step Tour’s step Base Object FALSE 
web_tour.tour Tours Base Object FALSE 
ir.cron.trigger Triggered actions Base Object FALSE 
utm.campaign UTM Campaign Base Object FALSE 
utm.medium UTM Medium Base Object FALSE 
utm.mixin UTM Mixin Base Object FALSE 
utm.source UTM Source Base Object FALSE 
utm.source.mixin UTM Source Mixin Base Object FALSE 
utm.tag UTM Tag Base Object FALSE 
_unknown Unknown Base Object FALSE 
base.module.update Update Module Base Object TRUE 
snailmail.letter.missing.required.fields Update address of partner Base Object TRUE 
crm.lead.pls.update Update the probabilities Base Object TRUE 
base.module.upgrade Upgrade Module Base Object TRUE 
res.users User Base Object FALSE 
bus.presence User Presence Base Object FALSE 
res.users.settings User Settings Base Object FALSE 
res.users.settings.volumes User Settings Volumes Base Object FALSE 
change.password.user User, Change Password Wizard Base Object TRUE 
change.password.own User, change own password wizard Base Object TRUE 
res.users.apikeys Users API Keys Base Object FALSE 
res.users.deletion Users Deletion Request Base Object FALSE 
res.users.log Users Log Base Object FALSE 
ir.ui.view View Base Object FALSE 
web_editor.converter.test.sub Web Editor Converter Subtest Base Object FALSE 
web_editor.converter.test Web Editor Converter Test Base Object FALSE 
resource.calendar.attendance Work Detail Base Object FALSE 
ir.websocket websocket message handling Base Object FALSE 
ODOO Odoo - Connection & Settings
Creates a record of a specific entity type, including custom entities.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Create Record
Connection*Select your connection or create one
Entity*Select the Entity where the new record will be created, e.g, “Contact”
Map Fields*
[+ Add Field]		Add various attributes to your Record with a dynamic field display. E.g., for the Entity Contact you can populate the fields Name, Address Type, Email.

(*) required field

Use this Method to delete a single Record by adding Matching Criterias. Return error when 0 or more than 1 record found.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Delete Single Record
Connection*Select your connection or create one
Entity*Select the Entity type to delete the record from, e.g, “Contact”
Matching Criteria*
[+ Add Matching]		Filter the record to delete by adding criterias from a dynamic list. E.g., “Name”, “Tax ID”, or “Email”.
Condition logic:Condition logic are related to Entities, which mean, different entities have different conditions logic available:

Equals – To retrieve or filter records where a field value exactly matches the specified input.

Does Not Equal – To exclude records with a specific value in a field.

Is Empty – Used to find records where a field is missing or hasn’t been filled.

Is Not Empty – Used to filter records where a field is populated with any value.

Like – Used for partial matches in fields like names or descriptions.

Not Like – Used to exclude records that contain certain text or patterns.

Greater or Equal – Used for numeric or date comparisons where values meeting or exceeding a threshold are required.

Greater Than – Used to find records with values above a certain threshold.

Lower or Equal – Used to filter records with values below or at a certain threshold.

Lower Than – Used to find records with values below a certain threshold.

Like (case sensitive) – To filter records containing specific patterns while considering uppercase and lowercase differences.

Like (case insensitive) – To perform broader searches where uppercase/lowercase differences are ignored.

Not Like (case sensitive) – To eliminate records that fit a specific pattern while respecting uppercase and lowercase.

Not Like (case insensitive) – To filter out records with a pattern regardless of case.
if not Found Consider as*:Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.
Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

Get A record detail by ID.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Get Record by ID
Connection*Select your connection or create one
Entity*Select the Entity type to get the record from, e.g, “Contact”
Matching Criteria
Record ID*Unique identifier of the record.

You can get the ID from a step response via input field, select “Responses tab” > Odoo response > ID
If Not Found Consider As:*Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

List all records from your Odoo Database, with optional filter.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*List Records
Connection*Select your connection or create one
Entity*Select the Entity type to retrieve records from, e.g., “Contact”
Matching Criteria
[+ Add Matching]		Add various attributes to your Entity, along with a dynamic list of available criteria, to filter the records.
Limit Record per pageSet the limit for the number of records retrieved. If not specified, it will retrieve the number of records defined by the API limit.
Record to skipAn integer value indicating the number of records to skip.
For example:
0: Start fetching from the first record.
5: Skip the first five records and start fetching from the sixth record.

(*) required field

Use this Method to Update a single Record by adding Matching Criterias. Return error when 0 or more than 1 record found.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name* Update a Record
Connection*Select your connection or create one
Entity*Select the Entity type to update the record from, e.g., “Contact”
Map Fields
[+ Add Field]		Add various attributes to your Record with a dynamic field display. E.g., for the Entity Contact you can populate the fields Name, Address Type, Email.
Matching Criteria
[+ Add Matching]		Add various attributes to your Entity, along with a dynamic list of available criteria, to filter the record for updating.
Condition logic:Conditions are related to Entities, which mean, different entities have different conditions logic available.

Equals – To retrieve or filter records where a field value exactly matches the specified input.

Does Not Equal – To exclude records with a specific value in a field.

Is Empty – Used to find records where a field is missing or hasn’t been filled.

Is Not Empty – Used to filter records where a field is populated with any value.

Like – Used for partial matches in fields like names or descriptions.

Not Like – Used to exclude records that contain certain text or patterns.

Greater or Equal – Used for numeric or date comparisons where values meeting or exceeding a threshold are required.

Greater Than – Used to find records with values above a certain threshold.

Lower or Equal – Used to filter records with values below or at a certain threshold.

Lower Than – Used to find records with values below a certain threshold.

Like (case sensitive) – To filter records containing specific patterns while considering uppercase and lowercase differences.

Like (case insensitive) – To perform broader searches where uppercase/lowercase differences are ignored.

Not Like (case sensitive) – To eliminate records that fit a specific pattern while respecting uppercase and lowercase.

Not Like (case insensitive) – To filter out records with a pattern regardless of case.

(*) required field

Use this Method to Update a Record from an Entity, if no record found, it will create a new one. 
Return error if multiple record found, for example: “More than one record match the ids [55,1,52,41,40]”. 

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Upsert Record
Connection*Select your connection or create one
Entity*Select the Entity to upsert the record in, e.g., “Contact”
Map Fields
[+ Add Field]		Add various attributes to your Record with a dynamic field display. E.g., for the Entity Contact you can populate the fields Name, Address Type, Email.
Matching Criteria
[+ Add Matching]		Add various attributes to your Entity, along with a dynamic list of available criteria, to identify the specific record for Upserting.
Condition logic:Conditions are related to Entities, which mean, different entities have different conditions logic available:

Equals – To retrieve or filter records where a field value exactly matches the specified input.

Does Not Equal – To exclude records with a specific value in a field.

Is Empty – Used to find records where a field is missing or hasn’t been filled.

Is Not Empty – Used to filter records where a field is populated with any value.

Like – Used for partial matches in fields like names or descriptions.

Not Like – Used to exclude records that contain certain text or patterns.

Greater or Equal – Used for numeric or date comparisons where values meeting or exceeding a threshold are required.

Greater Than – Used to find records with values above a certain threshold.

Lower or Equal – Used to filter records with values below or at a certain threshold.

Lower Than – Used to find records with values below a certain threshold.

Like (case sensitive) – To filter records containing specific patterns while considering uppercase and lowercase differences.

Like (case insensitive) – To perform broader searches where uppercase/lowercase differences are ignored.

Not Like (case sensitive) – To eliminate records that fit a specific pattern while respecting uppercase and lowercase.

Not Like (case insensitive) – To filter out records with a pattern regardless of case.

(*) required field

ODOO Odoo - Connection & Settings
Use this Method to delete multiple Records by adding Matching Criterias.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Delete Multiple Records
Connection*Select your connection or create one
Entity*Select the Entity where the records will be deleted from, e.g, “Contact”
Matching Criteria*
[+ Add Matching]		Filter the records to delete by adding criterias from a dynamic list. E.g., “Name”, “Tax ID”, or “Email”.
Condition logic:Conditions are related to Entities, which mean, different entities have different conditions logic available:

Equals – To retrieve or filter records where a field value exactly matches the specified input.

Does Not Equal – To exclude records with a specific value in a field.

Is Empty – Used to find records where a field is missing or hasn’t been filled.

Is Not Empty – Used to filter records where a field is populated with any value.

Like – Used for partial matches in fields like names or descriptions.

Not Like – Used to exclude records that contain certain text or patterns.

Greater or Equal – Used for numeric or date comparisons where values meeting or exceeding a threshold are required.

Greater Than – Used to find records with values above a certain threshold.

Lower or Equal – Used to filter records with values below or at a certain threshold.

Lower Than – Used to find records with values below a certain threshold.

Like (case sensitive) – To filter records containing specific patterns while considering uppercase and lowercase differences.

Like (case insensitive) – To perform broader searches where uppercase/lowercase differences are ignored.

Not Like (case sensitive) – To eliminate records that fit a specific pattern while respecting uppercase and lowercase.

Not Like (case insensitive) – To filter out records with a pattern regardless of case.
If Not Found Consider As:*Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

Update multiple records from a specific Entity.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a previous step.
  • Default Value: You can specify a fixed attribute.
Name*Update Multiple Records
Connection*Select your connection or create one
Entity*Select the Entity type to update records from, e.g., “Contact”
Map Fields
[+ Add Field]		Add various attributes to your Record with a dynamic field display. E.g., for the Entity Contact you can populate the fields Name, Address Type, Email.
Matching Criteria
[+ Add Matching]		Add various attributes to your Entity, along with a dynamic list of available criteria, to filter the records for updating.
Condition logic:Conditions are related to Entities, which mean, different entities have different conditions logic available:

Equals – To retrieve or filter records where a field value exactly matches the specified input.

Does Not Equal – To exclude records with a specific value in a field.

Is Empty – Used to find records where a field is missing or hasn’t been filled.

Is Not Empty – Used to filter records where a field is populated with any value.

Like – Used for partial matches in fields like names or descriptions.

Not Like – Used to exclude records that contain certain text or patterns.

Greater or Equal – Used for numeric or date comparisons where values meeting or exceeding a threshold are required.

Greater Than – Used to find records with values above a certain threshold.

Lower or Equal – Used to filter records with values below or at a certain threshold.

Lower Than – Used to find records with values below a certain threshold.

Like (case sensitive) – To filter records containing specific patterns while considering uppercase and lowercase differences.

Like (case insensitive) – To perform broader searches where uppercase/lowercase differences are ignored.

Not Like (case sensitive) – To eliminate records that fit a specific pattern while respecting uppercase and lowercase.

Not Like (case insensitive) – To filter out records with a pattern regardless of case.

(*) required field

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.

Important 01 Odoo - Connection & Settings

Going further Copy Link

Explore the full Wiresk User Guide to learn more.

Looking for an integration that’s not yet available? Submit a request to our team, we’ll do our best to support your needs.