topic Re: Custom Connector size limits in Workato Pros Discussion Board

Custom Connector size limits

dferguson — Fri, 29 Jan 2021 03:20:23 GMT

Does anyone know of an upper bound on the number of actions a custom connector can have or the size of the custom connector ruby file?

Re: Custom Connector size limits

amlan — Fri, 29 Jan 2021 04:39:18 GMT

My initial response is that there shouldn't be any limits. Why do you ask Dan F? Have you faced an issue or are you planning to build one with lots of actions?

Bennett Goh Chandra V are the experts. If we don't mention it in our docs, we should.

Re: Custom Connector size limits

adrian-chong — Fri, 29 Jan 2021 06:41:15 GMT

Keen to know if there are any limits as well. FYI Dan Ferguson I've started out with 17 actions, no issues.

Re: Custom Connector size limits

chandra — Fri, 29 Jan 2021 12:25:56 GMT

Hi Adrian,

We don't have any size limits on the number of actions or triggers in the custom connector and even the length of the file.

we have cases we built 50+ actions e.g. Coupa, but we converted to grouping approach later for seamless user experience.

we suggest grouping (actions/triggers) approach when there are tons of objects to be supported in the connector(e.g. Salesforce).

You can define actions like:

Actions:

Create record,

Search records,

Update Record,

Get Record details by ID.

Triggers:

New record

New/updated record

The details documented Workato's advanced connector building guide section.

Re: Custom Connector size limits

dferguson — Fri, 29 Jan 2021 22:38:26 GMT

This relates to the question asked here: https://community.workato.com/main/groups/44978/lounge/posts/634780?tab=comment

I am planning on generating our APIs endpoints from the OpenAPI spec. Based on some intial testing I am looking at 300-400 actions each with a custom input and out model. The search functionality seems like a it would work great as long as there is not a limit on actions.

Re: Custom Connector size limits

harish — Sat, 30 Jan 2021 03:02:17 GMT

You can implement single action patern (much like the Create record pattern in Saleforce connector) to avoid generating a large scaffolding code. This way the code generated will be smaller and easier to manage/debug etc.