After the deadline when Integration for Sentence Builder was deprecated at the end of March, is the “Use deprecated API payload” option still supported?
Additionally, if the migration is successful, do we need to reconfigure or reset all existing automations on the boards?
Best answer by noa.rapoport
Hi!
Regarding your first question: yes, the deprecated API option will remain available until further notice. That said, it won’t support new changes, and certain updates to your app may break it. We strongly recommend aligning your backend with the new infrastructure when possible, it’ll save your future self some time 🙂
Regarding your second question: you don’t need to rebuild existing automations at this stage. As long as you continue to support the legacy feature (which will remain editable until further notice), any automations already built will continue to run. However, this does mean you’ll need to maintain support for both infrastructures on your end.
If the migration is successful and you have the capacity to rebuild the automations, doing so would eliminate the need to maintain two infrastructures and reduce the effort required to migrate running automations in the future.
Hi!
Regarding your first question: yes, the deprecated API option will remain available until further notice. That said, it won’t support new changes, and certain updates to your app may break it. We strongly recommend aligning your backend with the new infrastructure when possible, it’ll save your future self some time 🙂
Regarding your second question: you don’t need to rebuild existing automations at this stage. As long as you continue to support the legacy feature (which will remain editable until further notice), any automations already built will continue to run. However, this does mean you’ll need to maintain support for both infrastructures on your end.
If the migration is successful and you have the capacity to rebuild the automations, doing so would eliminate the need to maintain two infrastructures and reduce the effort required to migrate running automations in the future.
+1Isn’t most of this just checking for both shapes of payload on your workflow actions?
Something like this:
// inputFields
const { inputFields } = body.payload;
// 👇 old shape 👇 new shape. 👇 not set
const boardId = inputFields?.boardId?.value ?? inputFields?.boardId ?? null;
const itemId = inputFields?.itemId?.value ?? inputFields?.itemId ?? null;
// Access token from credentials
const accessToken = body.payload.credentialsValues?.someToken?.accessToken ?? null
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.