[New Plugin] ICS Parser - iCalendar file (.ics) parser

Hey Muneer,

I’m facing the same issue with Oliver, except, my issue with using the date format you provided ‘YYYMMDD’ is that I am unclear what timezone the dates are parsed into. Ordinarily this wouldn’t be an issue, unless you have an app with users in different timezones and you want it optimized based on each user’s timezone preferences. Is there a json/text output that parses the date in to Data Type?

Hi @inphynx

You don’t have to use the prebuilt calls. You can use the ics to json parser and handle any nuance you want. If you go to the playground and scroll to the bottom, you can test there. Only difference, if you will need to pass that JSON to yourself so bubble can interpret it for your use. Hope this helps.

1 Like

Thanks for the response. I’ve used the ics parser and now I have the JSON output, however I don’t know how to pass JSON back to myself for bubble to interpret.
Aside using API connector, which I don’t think it applies in this case (if it does please let me know). Do you have any resources that can help me figure it out?

Update:

I just used the API connection you used in your plugin and it works good now. Thanks.

1 Like

Hey @muneer.hameer, I have a question… or more of a request. So the returned json from the API is nice, however, I see on the instruction page for using ICS parser, one of your returned values for your predefined types (specifically Dates Parsed as “Text” type) shows in the ISO 8601 format.

Is there a way for the API to return dates in the full ISO 8601 format as well, rather than the 20240202 format?

I find that’s way easier to work with.

Hey @muneer.hameer, I figured out how to turn the text into date format in the end. Thanks for your time.

1 Like

Hey @muneer.hameer I’m trying to use the plugin which looks great but I’m having a problem with a specific use case.

I need to save and sync an Airbnb calendar. My issue is that I’m not able to run the workflow API on the json (ics2json) because Bubble doesn’t recognize the type of things.

How do I let them Bubble know the type of things of the json?

Hi

Couple ways to approach this:

  1. Set up a backend workflow for the ics2json action
  2. Expose that api to public
  3. Set up an API call to that workflow in the API connector (it is sort of circular as you are calling your own backend wf in the api connector)
  4. Call the API and save the response
  5. Then use that API call in your future workflows to obtain and read the json response.

Or

Get a plugin like JSON assistant that will let you work with the json response from the plugin.

Hope this helps.

@muneer.hameer I’m currently testing this for Airbnb, Do you have an .ics link for testing?

@muneer.hameer Please remove this from the preset. Even when overwriting with a dynamic input field, the path URL remains the ICS source.

I’m sorry, I don’t have a sample.

I’ll look into your other comment. Those calls have been part of the plugin for a long time and it’s the first time I’m hearing of such an issue. If you are replacing with a dynamic input that’s not empty, not sure why it would reference the preset, unless it’s some bubble bug.

@muneer.hameer the bug is consisntely present on "Data VEEVENT (ICS Parser) and not "Data (AirBnB variant VEEVENT).

When I put any static text in (path) url, it works as expected, however when I put a dynamic input field (the way it should be) the default “s3.amazonaws.com/appforest_uf…” is the data that gets pulled

Hi there, I pushed an update removing those preset urls. Can you update the plugin and let me know if it resolves your issue. This sounds like a bubble bug, not the plugin.

@muneer.hameer that worked! Appreciate the quick resolution!

1 Like