This topic was automatically generated from Slack. You can find the original thread here.
Also for the “pipedream” app when/why is that needed? For example in the Microsoft Calendar Upcoming Event trigger, there are two app fields, one for microsoft_calendar (makes sense), and the other for pipedream. Should pipedream be our integration for pipedream?
backend-1 | configuredProps [
backend-1 | {
backend-1 | "name": "microsoftOutlook",
backend-1 | "type": "app",
backend-1 | "app": "microsoft_outlook_calendar"
backend-1 | },
backend-1 | {
backend-1 | "name": "http",
backend-1 | "type": "$.interface.http",
backend-1 | "customResponse": true
backend-1 | },
backend-1 | {
backend-1 | "name": "db",
backend-1 | "type": "$.service.db"
backend-1 | },
backend-1 | {
backend-1 | "name": "timer",
backend-1 | "type": "$.interface.timer",
backend-1 | "label": "Webhook renewal timer",
backend-1 | "description": "Graph API expires Outlook notifications in 3 days, we auto-renew them in 2 days, [see](https://docs.microsoft.com/en-us/graph/api/resources/subscription?view=graph-rest-1.0#maximum-length-of-subscription-per-resource-type)",
backend-1 | "default": {
backend-1 | "intervalSeconds": 172800
backend-1 | }
backend-1 | },
backend-1 | {
backend-1 | "name": "pipedream",
backend-1 | "type": "app",
backend-1 | "app": "pipedream"
backend-1 | }
backend-1 | ]
If you’re deploying this through Connect, this source is currently not supported. It uses the pipedream app field because it uses a subscription model (very very few sources do this).
I see, bummer
We already have an issue being worked on to get a polling version of this source so that it is supported in Connect.
Nice, that’s great
FWIW, I don’t even think this current subscription one works correctly either
So will be good to replace either way
Is polling the preferred model for sources?
It should work normally when deploying via Pipedream (via the workflow builder)
I was testing it myself last week
Interesting, the event must “update” when the reminder time triggers
It should work for any upcoming events, whether created/updated before the source was deployed or not
And re: preferred model, webhooks are usually best. Polling is an alternative for when webhooks aren’t available
Seems like the new email uses subscription as well - but can be deployed over connect, is that basically just a bug in the “new email” one? Since the subscriptions theoretically need to be renewed every few days otherwise microsoft expires them?