🔎 Algolia Search V2.0 - Major Plugin Update from Zeroqode

[florian.adomeit]

Update: As suggested, I have created a corresponding key with which the deletion works without any problems. Thank you very much for your help!

[ZeroqodeSupport]

Hi @florian.adomeit,

If the Write API Key has enough permissions for the use case you are using, feel free to use it and not create a new key. We provided this as an example and suggestion not to interfere with the other keys you might have

The YouTube videos will never be 100% accurate as multiple updates have been released. We are not sure why the backend actions are using the specific key, but we will make sure to remember this behavior.

If you have any other questions or concerns, feel free to reach out to us anytime via the forum here or at support@zeroqode.com

Best regards

[gabriel.pavan]

Hello,

Good afternoon! I would like to know if you could provide a more detailed example of how the Algolia Search 2.0 plugin can be used in a job search use case.

Any insights or step-by-step guidance would be greatly appreciated!

Thank you in advance for your help.

[ZeroqodeSupport]

Hey @gabriel.pavan ,
Thank you for contacting us.

We have already answered your question on our forum.
Please check it out and let us know if you have additional questions.

Have a great day!

Best Regards,
Zeroqode Support Team

[aaron.castells]

Hi! How i can set the “facet” attribute of the query? I want to know how many hits for each facet value.

[ZeroqodeSupport]

Hi @aaron.castells ,

Thank you for your question!

To configure and use the “facet” attribute in Algolia, here’s what you need to do:

Attributes for Faceting

Faceting is a powerful feature in Algolia that allows you to categorize your data based on specific fields, such as company, language, or country. To enable faceting:

1. Open the Search Tab

• Go to your Algolia dashboard and navigate to the Search tab.

2. Configure Facets

• Under the Configuration section, select Facets and add the attributes you want to filter by.
  
  

Querying Facets

When making a query, you can use the facetFilters parameter in your API request to filter results based on specific facet values. To retrieve the number of hits for each facet value, ensure the attributes you’ve set for faceting are correctly defined in your configuration.

Hits Per Page

You can control the number of results displayed per page using the Hits Per Page setting. While the default value is 10, you can override this at query-time by providing a new value in your API request.

Attributes to Retrieve

If you want to limit the attributes returned in the response, you can use the attributesToRetrieve parameter. By default, all attributes are returned, but you can specify only the ones you need.

For more details, feel free to check our Algolia Documentation.

If you have further questions feel free to reach out!

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble

[ZeroqodeSupport]

Hello everyone,

We hope you’re all enjoying the holiday season.

As data security is a big priority to all people, we’re always working to improve our plugins to ensure they’re as secure as possible. We’re excited to announce that Algolia Search V2.0 has received an important update, and version 3.70.0 is now available! In this update, we’ve restructured the plugin to enhance its security and streamline functionality.

Here are some of the key changes in the latest version:

1. We’ve separated the key fields to ensure the search key and permission key are used correctly.
2. We’ve removed all client-side actions that require higher-level keys.
3. We’ve transitioned the actions for “Delete Object,” “Add Object,” and “Update Object”.

If you’re using client-side actions for modifying, deleting, or adding objects, we recommend updating the plugin to take advantage of these improvements. The setup process remains the same as before, so the transition should be quick and easy.

We encourage you to thoroughly review our demo editor page and documentation to ensure a seamless and successful plugin integration.

Your feedback is very important to us, so please don’t hesitate to reach out with any questions or concerns. We’re always happy to assist!

Best regards, and Happy Holidays!
Support Team
Browse all Zeroqode Plugins for Bubble

[aaron.castells]

yes but i need the facets in the plugin response and in order to appear in the api call that the plugin does it should send the “facets” parameter, I attached an image of the parameter missing in the plugin.

[ZeroqodeSupport]

Hi @aaron.castells ,

Thank you for your message!

Since the plugin doesn’t natively include the “facets” parameter in its API call, the facets won’t appear in the response by default. To have the filtering option from the “Algolia Search” element working correctly, you’ll need to set up filtering and faceting in the Algolia Dashboard.

As a workaround, you can use Bubble’s API Connector to manually create an API call to Algolia, include the “facets” parameter, and retrieve the necessary data.

Example API Request:

{  
  "query": "<your_search_query>",  
  "facets": ["facet_field_1", "facet_field_2"],  
  "maxFacetHits": 10  // Optional: limit number of facet results  
}  

For more details on setting up attributes for faceting in Algolia, you can refer to their official documentation here: Attributes for Faceting - Algolia Documentation

Let me know if you need further assistance or if you have any other questions

Best Regards,
Support Team
Browse all Zeroqode Plugins for Bubble

[ZeroqodeSupport]

Hi @aaron.castells ,

We wanted to follow up and see if you’ve had a chance to go over the steps we shared earlier. If the issue persists or if there’s anything else you’d like help with, please don’t hesitate to let us know.

We’re always here to assist and would be happy to help address any challenges you might be facing.

Looking forward to your reply!

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble

[andrewmccalister]

I have a question on backend delete.

Ran into this error. Can you advise:

From the logs it looks to be passing the object ID correctly.

How I’m running the workflow:

How I’m sending data to the workflow. I presume it’s the ‘:split by’ that’s causing an issue here. I’m unsure why though.

[ZeroqodeSupport]

Hi @andrewmccalister

Thanks for reaching out! !

The error message seems to point to an issue with handling the data, especially with how the :split by is used to process the unique_id_inspo values. Here are a few things to check and adjust:

Ensure Correct Formatting in Split Values

• The :split by operator divides a text into a list, but it needs to match the exact format. Check that the unique_id_inspo values are properly formatted before you attempt to split them. If there are any null or empty values in the list, that could be causing the issue.

Check for Null Values in the List

• If there are any null values in the list after splitting, it could lead to errors when trying to process them in the workflow. You may want to add a conditional check (e.g., “only when”) to ensure the values are not null before passing them into the delete action.

Verify Object ID

• Double-check that the unique_id_inspo values you’re passing to the delete action are the correct IDs for the objects you want to delete. You might want to confirm that you’re passing the correct data type (text or a list of texts) into the Delete Objects action.

Debugging

• If you haven’t already, We’d recommend adding some debug logs or using a “Text” element temporarily in your workflow to display the data you’re sending and ensure it’s in the expected format (a list of IDs). This will help you pinpoint where the issue occurs.

Looking forward to your reply.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble

[rosshelton]

Hello,
Is is possible to use this in your plugin?
restrictSearchableAttributes

I would like my end user to have the option to specify if they only want to search one field instead of all fields.

[ZeroqodeSupport]

Hi @rosshelton ,

Thanks for reaching out!

Yes, Algolia does support the restrictSearchableAttributes parameter, but at the moment, our Algolia Search V2.0 Plugin does not have built-in support for this specific option. However, there are a couple of possible workarounds you can try:

Possible Workarounds:

Use Algolia’s “Searchable Attributes” Setting in the Dashboard

• In your Algolia Dashboard, you can configure searchable attributes for your index.
• If you want users to search only within specific fields, you can prioritize certain attributes by setting them up in Algolia’s index settings.

Filter Search Results on the Frontend

• If you want to allow users to select a specific field to search, you can apply post-processing filters in Bubble after retrieving the results.
• For example, you could return all results but display only those matching the selected attribute.

Use Multiple Algolia Indexes

• Another approach is to create separate indexes in Algolia—each with different searchable attributes.
• Then, depending on the user’s selection, run the search on the relevant index instead of restricting attributes dynamically.

For further guidance, feel free to check out our documentation and demo page:
Docs: Algolia Search V2.0 Plugin Documentation
Demo: Live Demo Page

Let us know if you need any further clarification. Happy to assist!

Best,
Support Team
Browse all Zeroqode Plugins for Bubble

[rosshelton]

Hi! Thanks for the reply. Unfortunately none of those will work for me based on my apps structure.

1. I really need it to ignore all fields my users chooses, not just prioritze.
2. This could work but it screws up my pagination. I have it going to the next returned set programmatically. Post filter will get screwy.
3. This also wont work because I would need to create a bunch of combos to allow my user to choose which to search and not.

Would it be possible to get this feature added? Even just a blank field that I can fill out with the json. An advanced section?

[ZeroqodeSupport]

Hi @rosshelton,

Thanks for your response and apologies for the delayed response over the weekend!

While this feature isn’t currently built into the plugin, we’re always open to improvements. If you’d like to request this as an enhancement, you can submit a feature request here:

Submit a Feature Request:
Feature Request Form

One of our managers will review it and get back to you with an estimate if it’s feasible to implement.

In the meantime, if you’d like to explore more about restrictSearchableAttributes, you can check Algolia’s official documentation here:

Algolia Docs:
Restrict Searchable Attributes

Let us know if you have any other questions—we’re happy to assist!

Best,
Support Team
Browse all Zeroqode Plugins for Bubble

[thethinklab.au]

I’ve got Algolia setup and working, displaying in an RG.

However, the RG is based on a list of texts (field1).

I want all fields to be available in each RG cell, however, trying to use Result as the data source doesn’t work. Does anyone know how to achieve this?

[ZeroqodeSupport]

Hi @thethinklab.au,

Thanks for your interest in our plugin! We’ve replied to your questions via email, so let’s continue our communication there to avoid any miscommunication!

We appreciate your understanding

Best regards

Browse all Zeroqode Plugins for Bubble