Skip to main content
Question

Problems migrating Sentence Builder

  • February 4, 2026
  • 3 replies
  • 62 views

Since monday.com announced the "Integration for sentence builder" feature were going to be deprecated, we have been experiencing a large number of problems migrating our apps to the new infrastructure.

 

On the one hand, many of the functionalities the legacy sentence builder had, and that we relied on to perform integrations, are not being migrated correctly because the functionalities of the new infrastructure do not include them, for example:

ColumnId not being supported in the new workflow



This has created significant challenges for our team and clients, and we would love to understand the recommended approach moving forward.

 

Not only this, but we are also having various problems with the integrations we have been able to migrate, not being able to use them correctly on the boards for different reasons.

Fail creating automation

 

Our team receives this message in many of the Apps that HAVE been correctly migrated in the App Center. 

This other error is also recurrent, in which we cannot choose a status as a trigger for the integration.

We can not select a status


Finally, we tried to use the new Automation Block to create automations from scratch with the native triggers provided by monday, but their functionality is very inconsistent, only allowing us to use the Automation Block in some cases while in others it doesn't.

To be precise, this week we have not been able to use the automation block with a native trigger from monday, while the past week we could.


To all this, we must add that since this new infrastructure was announced, several of our clients have been experiencing failures in their integrations (not yet migrated) as well as in webhooks and other automations.

 

Has anyone found a workaround for this?

Is Monday planning to restore support for these legacy capabilities?

 

3 replies

dvdsmpsn
Forum|alt.badge.img+1
  • Participating Frequently
  • February 4, 2026

Workflows when they work, are really straightforward. When they start misbehaving, they are the most frustrating thing. 

On top of this, the documentation is not ready yet and far from complete. 

If you are looking at timescales for getting things working, I started a building a new workflow action in November that took 2 months of massive frustration before it was working acceptably and repeatably so that I could release it as a new feature. 

Having said that, the first automation I migrated in July was really easy as everything just worked, so I got that done in a few hours including learning how workflows & workflow credentials work. 

What was the difference? The complexity. Both connected to external systems, but the more recent one used object fields https://developer.monday.com/apps/docs/object-fields. And there’s so much that’s undocumented there eg. Static fields just do not work. Well they didn’t November-January. Remote fields are only documented in a way to show the very basics, so are mainly not usable unless you already have the specific domain knowledge. 

In my testing, remote fields sometimes just failed to render and did not send a request to the remote endpoint, so did not show up in the workflow.

Having said that, I think that remote fields (rather than static fields) are the way to go with object fields, because you can just build them in your app  if something changes, update the app rather than poking the developer center UI & the fields should appear in the workflow. Not having to use the UI to update your config is super cool.

I think a lot of the bugs may have been fixed, but some may not. I’ve seen bugs on the front end, in the developer center UI, and in the workflows themselves. At one point I was producing several Looms per day to add to support tickets for bugs in workflows. Thankfully the volume of tickets I’m submitting now is lower than it has been. 

The timescale of the changeover is a rather aggressive goal to achieve successful migration of all apps to the new infrastructure. 

I believe that this project has been a lot harder than anyone expected, and there’s still a lot to do before the old infrastructure gets turned off. 

Oh, and I’ve not used the migration tool as it’s not helpful for our specific case with external integrations and OAuth. 


Revilre
Forum|alt.badge.img+1
  • February 4, 2026

The “status is something”, is a dependency. In all of this effort, it seems the limitation of the old automation builder for dependencies like this wasn’t fixed. Historically only the preformed recipes where you set the dependencies manually could have a dependency - including the status value on the column id.

I was under the impression that static recipes are staying for the time being, and it is only the old automation builder being deprecated. Is this true?


OmerK
Forum|alt.badge.img+1
  • monday.com Team Member
  • February 5, 2026

Forwarded to the migration group

@maorko could you please have a look?