We're excited to announce the release our new BigCommerce data source ! BigCommerce is a powerful e-commerce platform that allows businesses to sell their products online. The component supports endpoints for orders, customers, brands, and products, and makes it easy to extract data from your Big Commerce store. Plus, it supports incremental loads, so you can keep your data up to date without having to extract everything each time.

If you have any questions or feedback, please do not hesitate to contact us.

We are pleased to announce the release of a new data source component, Microsoft Advertising (Bing Ads), which allows you to easily retrieve data from all report types available on the Microsoft Advertising platform. This new component replaces the old public Bing Ads extractor (esnerda.ex-bingads), which will be deprecated and no longer supported. However, the old component will still be functional.

The new Microsoft Advertising component comes with many user interface and user experience improvements. It does not require users to provide a Developer Token anymore, making it easier to use. Moreover, the report data can be downloaded incrementally, allowing for automated retrieval of increments. Users can either define a custom report or use one of the predefined presets.

Due to some structural changes, there is no automated migration available at this time. However, the result data should have the same structure as in the old component. If you require assistance with migration, please do not hesitate to contact our support team.

The new component allows you to define custom reports or use on of the presets available:

• Account Performance
• Account Impression Performance
• AdGroup Performance
• AdGroup Impression Performance
• Campaign Performance
• Campaign Impression Performance
• Product Dimension Performance
• Keyword Performance
• Geographic Performance

We hope that the new Microsoft Advertising component will improve your experience. If you have any questions or feedback, please do not hesitate to contact us.

We are excited to announce the release of the Rename Columns Processor! This processor allows you to rename columns for specific tables or multiple tables defined by a wildcard. It takes all tables in the in/tables folder, renames specified columns in specified tables, and moves the result to out/tables. All other tables that are not specified or columns that are not specified will be moved unchanged. The in/files folder is also moved unchanged. Manifest files are respected and transferred/modified as well.

The typical usecase would be to rename only one specific column so it matches the requirements of Keboola Storage, e.g. when it's too long or contains forbidden characters and you want to control the resulting name. This is more suitable than Create Manifest processor for these purposes because you can selectively choose only specific tables.

Hi all, we have just published a new processor Drop Columns that is useful when you want to exclude some columns from your incoming sources (e.g. PIIs that you do not need).

To use this you can just add this processor into the after section. The bellow configuration excludes columns Location and Type from all tables that start with test prefix, e.g. test.csv:

{
  "definition": {
    "component": "kds-team.processor-drop-columns"
  },
  "parameters": {
    "table_mapping": {
      "test*": [
        "Location",
        "Type"
      ]
    }
  }
}

Note that the table name must match what the component output in the data/out/tables . The easiest way to see that is to run a debug job 

Hi all. We would like to create a new version of the BingAds (MS Advertising) extractor that is more stable, with improved UI/UX and some additional functionality. Is there anyone who uses it frequently and has some suggestions on what we may do differently? We are also in search of some testers that would help us to tune the new version on live data. 

Thank you

Hello community! We are about to start work on new Huspot (CRM, Sales) Extractor V2 and we'd like your input on what can be improved. Now is the chance to tell us what features you're missing or what can be done differently. Here's what we plan to change so far:

• Migrate to API V3 where possible (better control on time range based incremental sync)
• Improved row based UI (Allowing native parallelisation, endpoint per row)
• New endpoints support:
  • Deal Line Items
  • Calls
  • Meetings
  • Owners
  • Tickets
  • Object associations for all supported objects.

Anything we missed? Also if you'd like to join testing of the new connector let us know.

Hi all, some of you are already using the Google Apps script that runs in Google sheet and creates option for the user to trigger a Keboola Orchestration directly from the sheet. We have created and updated version of that which supports the new queue, e.g. Orchestrations v2 or Flows. 

Here's a guide on how to deploy it in you sheet:

1. Navigate to Extensions -> Apps script
2. Insert the entire code into the Code.gs (replace the existing content)
   1. Find the script attached on the post.
3. Save
4. Refresh or reopen the sheet.
5. New tab named Keboola will appear.
6. Hit reset settings.
7. Once you click Run orchestration you will be asked to provide url to your orchestration + Storage token (that will be saved for next run)
8. Now you can trigger your orchestration to collect the data directly from the sheet

Hello community, we have a new Zoho CRM extractor component ready for Beta testing. Is there anyone who would be willing to be part of the testing? 

Your help will be much appreciated and we'll be able to tune it to your liking.

Thank you!

Hi everyone, for all Czechs around you may find useful this new processor  we recently published. It allows you to process PDF account statements issued by Komercni Banka and store them in tabular form in Storage! It works best in combination with the IMAP Email Content datasource. Just schedule the statements to your email and set up the configuration.

Hi community! I am pleased to announce that we just added a new data source component that allows you to extract layout data from the FileMaker relational database via FileMaker Data API.