How can you trigger an Integration Procedure from a FlexCard action?

How can you trigger an Integration Procedure from a FlexCard action?

• A. Use a wait step.
• B. Directly edit the Integration Procedure code.
• C. Use a DataRaptor Transform.
• D. Configure a Card Action or Card Button in the FlexCard to call the Integration Procedure with the required inputs.

Answer: (D)

To trigger an Integration Procedure from a FlexCard, you configure a Card Action or Card Button on the FlexCard to call the Integration Procedure and pass the required inputs. The card action is the built-in bridge between the client-side card and server-side logic, so selecting the IP and mapping its inputs from the card’s data or user input lets the IP run on the server and return results that can update the card or trigger subsequent actions. The other approaches don’t provide this direct mechanism: a wait step lives inside the IP flow, not as a way to start it from the card; editing the Integration Procedure code isn’t how you initiate it from the UI; and a DataRaptor Transform is for data shaping, not triggering an IP from the card.

To trigger an Integration Procedure from a FlexCard, you configure a Card Action or Card Button on the FlexCard to call the Integration Procedure and pass the required inputs. The card action is the built-in bridge between the client-side card and server-side logic, so selecting the IP and mapping its inputs from the card’s data or user input lets the IP run on the server and return results that can update the card or trigger subsequent actions. The other approaches don’t provide this direct mechanism: a wait step lives inside the IP flow, not as a way to start it from the card; editing the Integration Procedure code isn’t how you initiate it from the UI; and a DataRaptor Transform is for data shaping, not triggering an IP from the card.