Invoke a Salesforce Apex Action From Titan Flow

Invoke a Salesforce Apex Action From Titan Flow

What Is a Salesforce Apex Action?

A Salesforce Apex action is a Titan Flow node that invokes a custom Apex class.

When the Flow reaches the node, Titan sends the mapped input values to Salesforce. Salesforce runs the Apex class and returns the configured results to Titan. You can then use these results in later nodes to update records, control routing, display messages, or continue the process.

This lets you reuse existing Salesforce logic instead of rebuilding the same calculations, validations, or business rules in Titan.

When to Use a Salesforce Apex Action

Use a Salesforce Apex action when your Flow needs to:

• Run a custom calculation or validation
• Apply a business rule already configured in Salesforce
• Process or update Salesforce data using custom logic
• Trigger functionality that is unavailable through standard Flow nodes
• Continue along a specific path based on the Apex response
• Reuse an existing Apex class across Salesforce and Titan processes

If you only need to retrieve, create, update, or delete Salesforce records, use a standard Salesforce action instead.

Use Case: Check Customer Eligibility Before Continuing

A customer submits a service request through a Titan form. Before the request can proceed, Salesforce must verify that the customer meets your organization’s eligibility requirements.

Your Flow sends the customer’s Salesforce record ID and request details to an existing Apex class. The class evaluates the information and returns an eligibility status.

Titan can then use the returned status to:

• Continue the request for an eligible customer
• Display a message when the customer is not eligible
• Update the Salesforce record
• Route the request for manual review

This keeps the eligibility rules in Salesforce while allowing Titan Flow to use the result at the correct point in the process.

How It Works

The Salesforce Apex action connects three parts of your process:

1. Titan input values: Form entries, Salesforce record IDs, system values, or Flow variables.
2. The Salesforce Apex class: The custom logic Salesforce runs using the supplied parameters.
3. Returned results: Values mapped back to Titan for use in later actions or conditions.

For example, you could send an Account ID to an Apex class, check whether the account qualifies for a service, and return an eligibility status. A condition node could then route eligible and ineligible customers along different paths.

Before You Begin

Make sure that:

• Titan is connected to the correct Salesforce organization.
• The Apex class is available in the connected Salesforce organization.
• You know the exact Apex class name.
• You know which parameters the class requires.
• You know which values the class returns.
• Your Flow contains variables or elements that can provide and store the required values.
• The connected Salesforce user has access to the class and related Salesforce data.

Contact your Salesforce administrator or developer if you are unsure about the class name, required parameters, returned values, or permissions.

Choose Where the Apex Action Runs

Where you add the Salesforce Apex node determines when the class runs.

In a Titan Web project, you can run an Action Flow:

• The first time a page loads
• Every time a page loads
• When a page-level variable changes
• When a user selects an element that supports an on-click action
• When an element condition is met
• At the project level, through a custom variable

For example, you could run an eligibility check when the user selects Submit. Place the Apex node after the form validation step but before any Salesforce update, message, or redirect that depends on the returned eligibility status.

Add the node after the steps that collect or prepare its input values. This makes sure the Apex class receives the information it needs when the action runs.

How to Configure a Salesforce Apex Action in Titan Flow

Add the Salesforce Apex Node

1. Select the + icon on the Action Flow node.
   The Add Node screen opens. Adding the Apex action at this point determines when the Salesforce logic runs in your Flow.
2. Select Salesforce.
3. Select Salesforce APEX.
   The Salesforce Apex node connects this part of the Flow to a custom Apex class in the connected Salesforce organization.

Create the Salesforce Integration

4. Select Salesforce Integration.
   The Salesforce Integration screen opens. This is where you create or select the integration that will call the Apex class.

5. Select Create New.
   The Map Salesforce Fields screen opens. Creating an integration lets you define the Apex class, its input parameters, and the results returned to Titan.

Select the Apex Class

6. From the Objects in Salesforce drop-down list, select Your APEX.
   This option tells Titan to invoke custom Apex instead of working with a standard Salesforce object.
7. Enter the exact Apex class name in the Class Name field.
   The name must match the Apex class available in the connected Salesforce organization.
8. Enter a description in the Description field, if required.
   Use the description to explain what the class does or why the integration is needed. A clear description makes the integration easier to identify when the project contains several Salesforce actions.

Note: The description appears below the integration under My Get Record Integration.

Map the Input Parameters

9. Select Parameters.
10. Map the Titan values that the Apex class requires.
    Parameters send the required information from Titan Flow to Salesforce. Depending on the Apex class, you may need to map:
    • A Salesforce record ID
    • An account or customer number
    • A value entered in the form
    • A status or selection
    • A custom variable
    • A system value
11. Match each Titan value to the correct Apex parameter. Missing values or incorrect data types may prevent the class from returning the expected result.

Map the Returned Results

11. Select Mapping.
12. Map each required result returned by the Apex class to a Titan value.
    Mapping the response makes it available to later Flow nodes. You can use the returned values to:
    • Evaluate a condition
    • Update a Salesforce record
    • Display a success or error message
    • Generate a document
    • Send an email
    • Redirect the user
    • Continue along a specific Flow path
13. If required by the Apex class, select the relevant values from the Current Device and Record ID drop-down lists.
    Use these mappings when the class requires information from the current session or a Salesforce record.
14. Select Apply, and then select Close.

Insert the Apex Action

15. From the Process push or get drop-down list, select Get.
    Select Get because Titan calls the Apex class and receives a response from Salesforce.
16. Select Next.

17. Enter a descriptive name in the Tag Name field.
    Use a name that explains what the action does, such as “Check Customer Eligibility” or “Calculate Renewal Amount”. Clear tag names make larger Action Flows easier to review, test, and maintain.
18. Select Insert.

Connect the Next Action

Connect the Apex node to the next step that should use its response.

Depending on your process, you could add:

• A condition node that checks an eligibility result
• A Salesforce action that updates a record
• A message that displays returned validation text
• A document generation action that uses a calculated value
• A redirect that sends the user to the appropriate page
• A manual review path for an unexpected response

If the Flow contains several branches, make sure each possible Apex result has a suitable path.

Test the Apex Action

Test the Flow with representative data before publishing it.

Confirm that:

• The Apex node runs at the correct point in the Flow.
• Titan sends the expected input parameters.
• Salesforce receives the correct values.
• The Apex class returns the expected response.
• Titan stores the results in the correct mapped values.
• Conditions and later actions use the returned values correctly.
• Missing or invalid inputs are handled appropriately.
• Salesforce errors do not leave the user without a message or next step.

Where possible, test successful, unsuccessful, missing-data, and unexpected-response scenarios.

Manage the Action Flow

Name every rule and add a descriptive tag to each node. This makes the process easier to understand without having to open every node to check its configuration.

You can also:

• Clone a rule when you need a similar sequence
• Turn rules on or off while testing
• Delete rules that are no longer required
• Use the map and zoom controls to move through larger Action Flows
• Save reusable sequences to the Action Flow Library

If you save a reusable rule to the library, add a Finish node. You can then use the rule in other parts of the project without rebuilding the complete sequence.

Frequently Asked Questions

Can I Use an Existing Apex Class?

Yes. You can call an existing Apex class if it is available in the connected Salesforce organization, supports the required inputs and outputs, and the connected Salesforce user has access to it.

What Can I Send to the Apex Class?

You can map Salesforce record IDs, form entries, system values, custom variables, and other Flow values. The mapped values must match the parameters expected by the Apex class.

Can I Use the Apex Response in a Condition?

Yes. Map the returned value to a Titan value and reference it in a condition node. This lets the Flow follow a different path based on the Apex response.

Why Is the Apex Action Configured as a Get?

Titan uses the Get option because the Flow calls the Apex class and receives mapped results from Salesforce. A standard Salesforce Push is typically used to create or update records.

What Happens if the Apex Class Returns an Error?

The result depends on how the Apex class and Flow are configured. Test error scenarios and add a suitable message or alternate path so users know what to do when the action cannot be completed.

Should Every Node Have a Tag Name?

Yes. Descriptive tags make the Flow easier to review, test, and maintain, particularly when it contains several Salesforce actions or conditional branches.

Can I Reuse the Apex Sequence Elsewhere?

Yes. If the Apex action is part of a longer rule that you need in several places, save the rule to the Action Flow Library and include a Finish node. This prevents you from rebuilding the same sequence each time.

Should I Use Apex for Standard Salesforce Record Actions?

Not necessarily. If you only need to retrieve, create, update, or delete Salesforce records, a standard Salesforce action is usually more suitable. Use Apex when your process requires custom Salesforce logic.

Related Articles

Trigger Titan Flow From Salesforce Flow

Connect Titan to Salesforce

Configure a Salesforce Action in Titan Flow

Create a Custom Variable in Titan Flow

Invoke Titan Flow From Another Flow