Text and image feeds share several settings. Options that apply only to one feed type are covered in their dedicated reference pages.
Name #
The administrative label for the feed. Use a name that explains the result or purpose, such as Summarize support request or Generate event banner. It appears in Form Settings, the GravityOps Feeds tab, entry rerun controls, logs, notes, and notification merge tags.
The feed’s Active/Inactive switch is managed by Gravity Forms outside the editor. Deactivating the feed prevents every way of running it.
API Key #
This setting appears only when more than one configured key source is available for the provider.
- Automatic prefers a server constant/environment value and otherwise uses the encrypted key saved through WordPress.
- Server configuration (constant/environment) deliberately chooses the server-managed key.
- The provider’s default profile deliberately chooses the key saved in WordPress.
If no selector appears, the feed uses Automatic because there is no meaningful alternative.
Model #
Choose a listed provider model appropriate to the feed type. The list uses these lifecycle labels:
- Recommended is the default the plugin recommends for new feeds.
- Superseded is the plugin’s label for an older model that the provider still marks active. It remains selectable, but the feed editor recommends considering its newer replacement.
- Legacy is reserved for a model the provider officially marks as legacy. It remains selectable with a stronger migration warning because it no longer receives updates and may be deprecated later. There are currently no provider-designated Legacy models in the supported Claude text or GPT Image families.
- Deprecated means the provider has announced that support will end. A deprecated model is hidden from new selections but remains visible, with its retirement date and replacement, on a feed that already uses it.
- Retired means the provider retirement date has arrived. The feed no longer sends generation requests until an administrator selects and saves a supported model.
The plugin never changes a feed’s model automatically. Model changes can alter behavior, capabilities, output limits, and provider charges, so an administrator must approve the replacement.
Active feeds using deprecated models also generate staged administrator alerts without requiring someone to revisit the feed editor. The Overview report is the persistent source of truth; the Feeds tab shows an affected count; consolidated notices appear on relevant administration screens; and lifecycle email is sent at first detection, seven days before retirement, and on retirement. The 30-day reminder is admin-only to reduce email volume. Inactive feeds appear in the report but do not generate notices or email.
Lifecycle data is shipped with plugin updates. The daily site scan does not independently discover provider announcements, so keeping the plugin current is part of receiving new lifecycle warnings.
Models differ in quality, speed, cost, maximum output, image options, and provider availability. Provider account permissions and region restrictions can also affect access.
Custom Model ID #
This field appears after choosing Custom model ID. Enter the exact API identifier published by the provider, for example an identifier copied from provider documentation or a models response. It is not a label you invent and it is not the model’s marketing name unless the provider uses that exact text as the API identifier.
Use it when a compatible model has been released but is not yet in the plugin catalog, or when a provider-supported model is intentionally absent from the normal list. The plugin cannot fully validate an unknown model’s capabilities or output limits. A text model must support the Anthropic Messages request used by the plugin; an image model must support the OpenAI Images request and selected image options.
A custom ID does not bypass a known retirement. If the plugin has reviewed that exact ID and its confirmed retirement date has arrived, the feed is blocked until a supported model is saved.
Trigger Mode #
Determines the normal event that starts the feed: after submission or a frontend button. It does not control administrator reruns or Gravity Flow steps. See the trigger and execution reference for exact behavior.
Conditional Logic #
Standard Gravity Forms feed conditional logic. When enabled, the feed runs only if the rules match the current entry values. Frontend buttons evaluate the values currently entered in the form. Administrator reruns and workflow steps evaluate the saved entry.
Conditional logic prevents the provider request when the condition does not match. Test both the matching and non-matching paths before publishing the form.
