Regarding Integrator.io connector public url

[deeptismitabehera]

Is there any chance to set the public url of integrator.io connector's public url in integrator.io. If yes how?

[kathyanaqueeman]

Hello @deeptismitabehera,

I'm moving this post to our Troubleshooting section for more visibility! Thanks!

[tylerlamparter]

@deeptismitabehera can you reword your question? I'm not sure what you're asking.

[geethakanawarathna]

Hi

Can i change the Public URL in webhhok listener

https://api.integrator.io/v1/exports/12545/data - Generated url.

i want to change it like ,

https://api.integrator.io/v1/exports/12545/data/config or https://api.integrator.io/v1/exports/12545/data/webhook

[tylerlamparter]

@geethakanawarathna for now, no that is not possible. What are you trying to solve by doing this? Are you wanting to route different event types by having in url itself? You could include event type in the post body and then branch in the flow.

[geethakanawarathna]

Ok. Thank you

[deeptismitabehera]

@tylerlamparter Actually in celigo we are having concept like listner ; Like we can use the public url of any saas app in the application to real time listener.. So Here I want to know if we can add the public url of the integrator.io connector for listner in celigo.

[rajithakumara]

Hi @tylerlamparter,

Good day to you. I adding to @geethakanawarathna's question to be more specific, and thought to continue same thread without creating new post. Hope it's fine.

We are trying to integrate our software with Teamtailor webhooks. So we are using Teamtailor partner APIs to implement this integration. Briefly, if a hiring manager moved a candidate to Hired stage in Teamtailor we want to trigger an event and listen from Celigo. We are following https://partner.teamtailor.com/partners/#teamtailor-partner-api documentation.

Mainly I want to know following items;

1. Is there existing connector on Celigo for Teamtailor ATS? (When I'm checking in connectors I couldn't find). Also can I know whether Teamtailor in your roadmap?

2. If we are to implement this integration, according to Teamtailor documentation we need to expose following endpoints GET ${BASE_URL}/config, GET ${BASE_URL}/activation, POST ${BASE_URL}/webhook. But as per our knowledge we can't define our own URL pattern for webhook listner Public URL in Celigo. Usually we are getting https://api.integrator.io/v1/exports/65b0a66c9deda91b232675az/******/data this pattern of URL. Here I can see following limitations in Teamtaillor and Celigo.

• Teamtailor limitation: We have to register one single ${BASE_URL} in Teamtailor configurations when registering webhook listner. So under that particular BASE_URL all three endpoints should support GET /config, GET /activation, POST /webhook. Here POST /webhook is the real webhook endpoint that we need to listen.
• Celigo limitation: We can't define our own URL pattern in the Public URL. I feel at least we should be able to define regex path or wildcard routing pattern e.g. https://api.integrator.io/v1/exports/65b0a66c9deda91b232675az/secret/data/.*

3. As you metioned if Celigo does not support this, is there any standard workaround for this problem. Maybe support wildcard routing. If these features are there in the roadmap I would be really happy to know.

Thanks in advanced

[tylerlamparter]

@rajithakumara thanks for the added clarity. It definitely makes more sense now. In this particular case, since you provide them a bearer token for the webhook authentication, you could actually use a MyAPI. so you create a MyAPI to handle the request, forward the request to a flow that has an IO listener on it, then respond back with the appropriate response. To setup your bearer token, you would go to resources>api tokens and create a new bearer token that only has access to that MyAPI. Here is a sample below:

import {exports} from 'integrator-api'

function handleRequest (options) {
  
  exports.run({
    _id: '65bbfae489fca84e68b581ea',
    listenerData: [options]
  })
  
  return {
    statusCode: 200,
    headers: { },
    body: options
  }
}

Sample flow:

MyAPI:

Postman example:

[rajithakumara]

Thanks @tylerlamparter for the in detail explanation. I'll try this out and see.

Thanks again.