Uncategorized

gravityflow_web_api_capability_get_entries_assignees

The gravityflow_web_api_capability_get_entries_assignees filter allows developers to customize the capability required to retrieve the assignees for a specific entry via the Gravity Flow Web API.

gravityflow_inbox_entry_detail_pre_process

The gravityflow_inbox_entry_detail_pre_process filter allows developers to control whether the entry detail should be processed before displaying it in the Gravity Flow inbox.

Name

The Step Name is a required setting in Gravity Flow used to identify each step in a workflow. It appears in the form editor, entry details, inbox and status views, exports, reports, and other key areas of your site.

Condition

The Condition setting lets you control whether a step should run or be skipped when the workflow reaches it. Similar to Gravity Forms’ field conditional logic, it uses entry values to determine if the step should be executed.

Settings (SMTP)

The Settings area Gravity SMTP allows you to manage all the core applications and integration settings.

Debug Log (SMTP)

This article explains how to access the Debug Log table in Gravity SMTP, as well as the process to send the information to our support team.

Scheduling a step

All steps can be scheduled by activating the Schedule setting. Scheduling can be useful when two steps are being triggered too close together, or when you need to perform a step on specific date.

Email Delivery Best Practices (SMTP)

This article covers best practices and recommendations for reliable email delivery with Gravity SMTP.

The Outgoing Webhook Step

The Outgoing Webhook Step, when triggered, sends entry values to a remote URL. Gravity Forms merge tags can be used in the Webhook URL, field mapping custom values, and in the raw request body.

System Requirements (SMTP)

Review this article to get familiar with the preferred system requirements for Gravity SMTP, and the minimum requirements expected to receive support.