Is there a way to ensure that integrations always run in a particular order? or otherwise hook them together?

[adrienne]

Question

I need for a value from one integration (a custom one which involves an API call) to get passed through to a different integration that creates an element. Is there a way to ensure that the API integration always runs first, or can you think of some other way i can accomplish this? Otherwise i'm going to have to copy and kitbash the default Formie Element integration into my custom integration, and that seems like a lot of duplication of effort. 😆

Additional context

No response

[engram-design]

It's not possible at the moment, really - sorry! Integrations are unable to communicate with each other, sending data from one to another.

I'd need to know a bit more detail about what your desired outcome would be, and which integrations. But extending the Entry element integration for example should take care of the bulk of things, allowing you to add your own handling.

There's probably complicated ways you could set things up.

You could first setup both your integrations as required. Using the beforeTriggerIntegration event, disable the running of the second integration automatically, to give you control over when it runs.

Then, in using the afterSendPayload event, listening on the first integration, and when it's been run, you manually call to trigger the second integration.

$integrations = Formie::$plugin->getIntegrations()->getAllEnabledIntegrationsForForm($form);

// Find the integration you need from the collection
$integration = integrations[0];

Formie::$plugin->getSubmissions()->sendIntegrationPayload($integration, $submission);

[adrienne]

So basically, the first integration is doing some third-party API stuff, including creating an object on the other end (in the third-party system). Said third-party system then sends back the ID of the newly-created object. That object ID needs to get stored inside the Entry created by the Entry integration.

[engram-design]

Fair enough - my suggestion above still stands! I imagine you're already writing your own custom integration.