Creating a Feed for the Highrise Add-On

Creating a Feed for the Highrise Add-On

SummaryCreate a FeedFeed Settings Screen

The Highrise CRM service is no longer in development, and no new accounts can be created. As of November 2019, we have deprecated the official Gravity Forms plug-in which is no longer available for download.

Summary
Before the Highrise Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, customer information being sent to Highrise.
Create a Feed
To create a feed to Highrise using the Highrise Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with Highrise.
Once within your desired form, hover over Settings and click on Highrise.
Click Add New to create a new feed. You will be presented with the Highrise feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshot below.

A Feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
Map Fields: Map each of the contact list fields to the desired form field that will contain that information. Use the custom dropdown to select additional field options.
The Contact Note field allows you to add a note the the newly created contact. You may use both static text, as well as marge tags to dynamically generate content.
The Contact Visibility field lets you use the dropdown to determine who is able to see the newly created contact.
Conditional Logic: If unchecked, every successful form submission will be sent to Highrise. If you wish to set specific conditions for sending form data to Highrise, then check the 「Enable」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Date Field CSS Selectors

Date Field CSS Selectors

Date Picker Input TypeInput FieldIcon ImageDate Field Input TypeMonthContainerInput FieldSub-LabelDayContainerInput FieldSub-LabelYearContainerInput FieldSub-Label

Date Picker Input Type
Input Field

example: date – input field (input) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .datepicker {border: 1px solid red}

example: date – input field (input) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .datepicker {border: 1px solid red}

example: date – input field (input) – applies just to specific date field input (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .datepicker {border: 1px solid red}

Icon Image

example: date – icon image (img) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_input_datepicker_icon {border: 1px solid red}

example: date – icon image (img) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_input_datepicker_icon {border: 1px solid red}

example: date – icon image (img) – applies just to specific date field input (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_input_datepicker_icon {border: 1px solid red}

Date Field Input Type
Month
Container
Contains the month input field and sub-label

example: date – month container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_month {border: 1px solid red}

example: date – month container (div) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_month {border: 1px solid red}

example: date – month container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_month {border: 1px solid red}

Input Field

example: date – month input field (input) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_month input {border: 1px solid red}

example: date – month input field (input) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_month input {border: 1px solid red}

example: date – month input field (input) – applies just to specific form field (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_month input {border: 1px solid red}

Sub-Label

example: date – month sub-label (label) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_month label {color: red}

example: date – month sub-label (label) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_month label {color: red}

example: date – month sub-label (label) – applies just to specific sub-label (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_month label {color: red}

Day
Container
Contains the day input field and sub-label

example: date – day container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_day {border: 1px solid red}

example: date – day container (div) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_day {border: 1px solid red}

example: date – day container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_day {border: 1px solid red}

Input Field

example: date – day input field (input) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_day input {border: 1px solid red}

example: date – day input field (input) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_day input {border: 1px solid red}

example: date – day input field (input) – applies just to specific form field (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_day input {border: 1px solid red}

Sub-Label

example: date – day sub-label (label) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_day label {color: red}

example: date – sub-label (label) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_day label {color: red}

example: date – sub-label (label) – applies just to specific sub-label (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_day label {color: red}

Year
Container
Contains the month input field and sub-label

example: date – year container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_year {border: 1px solid red}

example: date – year container (div) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_year {border: 1px solid red}

example: date – year container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_year {border: 1px solid red}

Input Field

example: date – year input field (input) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_year input {border: 1px solid red}

example: date – year input field (input) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_year input {border: 1px solid red}

example: date – year input field (input) – applies just to specific form field (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_year input {border: 1px solid red}

Sub-Label

example: date – year sub-label (label) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_year label {color: red}

example: date – year sub-label (label) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_year label {color: red}

example: date – year sub-label (label) – applies just to specific sub-label (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_year label {color: red}

Creating a Feed for the Square Add-On

Creating a Feed for the Square Add-On

Pre-RequisitesIntroductionCreate Your FeedTransaction TypesProducts and ServicesSubscriptionsProduct And Services SettingsPayment AmountAuthorize OnlyOther SettingsBilling InformationConditional LogicNotes

Pre-Requisites

Setup the Square Add-On
Create a Square Compatible Form

Introduction
The last step of integrating Square with Gravity Forms is creating a feed. A feed communicates information to Square each time a visitor successfully submits your form. This is a critical step, as without it, no data is sent to the external service.
Create Your Feed

Open your Square compatible form and from the dropdown menu, choose Settings → Square.

On the Square Feeds screen, select Add New.

On the Feed Settings screen, provide a unique Name.
Note: The feed name is not displayed to the user, but helps you distinguish the feed within admin lists.

Select a Transaction Type.Refer to the section below for an explanation of the transaction types.

Complete any panels of Feed Settings.Refer to the section below for a description of these settings.

Click Update Settings to finish saving your feed.

Transaction Types
The following transaction types are offered:
Products and Services
These are single/one-time payments.
Subscriptions
Subscriptions for Square can be created and managed via Gravity Forms
Product And Services Settings
The options offered here will be dependent upon the Transaction Type selected.

Payment Amount
Determines which form field will be used for the payment amount. For example, you could choose a specific product Field, or the form Total.
Authorize Only
This option allows Square to authorize the payment on a customer』s card, but to not capture that payment until a later date. Refer to this article for details.
Other Settings
Billing Information

Map your form fields to the Square address fields to determine what information will be sent to Square for each required billing field. This will include your Email Field, Name Fields and Address Fields.

Conditional Logic
Selecting 「Enable Condition」 checkbox allows you to specify the rules that determine when this feed executes.
Conditional Logic also allows you to configure multiple Square Feeds for a single form and trigger the correct one based on Conditional Logic.
Refer to the Conditional Logic feed article for more information.
Notes

Your Gravity Forms Currency Settings must match the Currency Settings in your Square account or you will not be able to create a feed.
Testing your Feed with a Square Sandbox Developer Account is highly recommended before testing your transactions on your live account first. See our article on Creating a Square Sandbox Account for Testing for more details.

Custom Field Merge Tags

Custom Field Merge Tags

SummaryUsageExample

Summary

Display a custom field value from the post/page the form was submitted from. These fields could be added through WordPress Custom Fields, through register_meta, or through a plugin like ACF, Pods or MetaBox.

Usage

{custom_field:[fieldname]}

Example

{custom_field:author_address} {custom_field:zipcode}

Creating a Feed for the Twilio Add-On

Creating a Feed for the Twilio Add-On

SummaryCreate a FeedFeed Settings Screen

Summary
Before the Twilio Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, form submissions being sent to the Twilio API.
Create a Feed
To create a feed to Twilio using the Twilio Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with Twilio.
Once within your desired form, hover over Settings and click on Twilio.
Click Add New to create a new feed. You will be presented with the Twilio feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshot below.

A feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
The From dropdown will list any phone numbers that are available within your Twilio account. Many users will only have a single number here to select, but if you have multiple numbers, select the number that you would like to use for sending notifications. Alternatively, you can select to use an Alphanumeric Sender ID if it has been enabled in your Twilio account』s SMS settings.
In the To Number field, enter the phone number that you would like notifications sent to. Be sure to include your fully numerical 10-digit phone number, including the area code. When selecting a phone field that uses the international format, the country code should be included in the number passed to the feed.
The Message field is the main part of the notification. Merge tags can be used to dynamically generate your notification message.
The Shorten URLs option will shorten URLs using Bitly. To use this option, you will need to configure Bitly support within the Twilio Add-On.
Conditional Logic: If unchecked, every successful form submission will be sent to Twilio. If you wish to set specific conditions for sending form data to Twilio, then check the 「Enable」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Credit Card Field CSS Selectors

Credit Card Field CSS Selectors

ContainerCard IconsContainerAmerican ExpressDiscoverMastercardVisaCard Number InputExpirationMonthYearSecurity CodeContainerInputIcon

Container
example: credit card field container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard {border: 1px solid red;}
example: credit card field container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard {border: 1px solid red;}
example: credit card field container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard {border: 1px solid red;}
Card Icons
Container
example: card icon container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container {border: 1px solid red;}
example: card icon container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container {border: 1px solid red;}
example: card icon container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .gform_card_icon_container {border: 1px solid red;}
American Express
example: card icon container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container .gform_card_icon_amex {border: 1px solid red;}
example: card icon container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container .gform_card_icon_amex {border: 1px solid red;}
example: card icon container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .gform_card_icon_container  .gform_card_icon_amex {border: 1px solid red;}
Discover
example: card icon container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container .gform_card_icon_discover {border: 1px solid red;}
example: card icon container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container .gform_card_icon_discover {border: 1px solid red;}
example: card icon container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .gform_card_icon_container  .gform_card_icon_discover {border: 1px solid red;}
Mastercard
example: card icon container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container .gform_card_icon_mastercard {border: 1px solid red;}
example: card icon container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container .gform_card_icon_mastercard {border: 1px solid red;}
example: card icon container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .gform_card_icon_container  .gform_card_icon_mastercard {border: 1px solid red;}
Visa
example: card icon container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container .gform_card_icon_visa {border: 1px solid red;}
example: card icon container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .gform_card_icon_container .gform_card_icon_visa {border: 1px solid red;}
example: card icon container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .gform_card_icon_container  .gform_card_icon_visa {border: 1px solid red;}
Card Number Input
example: card icon container (input) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_full input {border: 1px solid red;}
example: card icon container (input) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_full input {border: 1px solid red;}
example: card icon container (input) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .ginput_full  input {border: 1px solid red;}
Expiration
example: card expiration container (span) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_expiration_container {border: 1px solid red;}
example: card expiration container (span) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_expiration_container {border: 1px solid red;}
example: card expiration container (span) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .ginput_expiration_container  {border: 1px solid red;}
Month
example: card expiration month (select) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_expiration_container .ginput_card_expiration_month {border: 1px solid red;}
example: card expiration month (select) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_expiration_container .ginput_card_expiration_month {border: 1px solid red;}
example: card expiration month (select) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .ginput_expiration_container .ginput_card_expiration_month {border: 1px solid red;}
Year
example: card expiration month (select) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_expiration_container .ginput_card_expiration_year {border: 1px solid red;}
example: card expiration month (select) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_expiration_container .ginput_card_expiration_year {border: 1px solid red;}
example: card expiration month (select) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .ginput_expiration_container .ginput_card_expiration_year {border: 1px solid red;}
Security Code
Container
example: card security code container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_cardinfo_right {border: 1px solid red;}
example: card security code container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_cardinfo_right {border: 1px solid red;}
example: card security code container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .ginput_cardinfo_right {border: 1px solid red;}
Input
example: card security code input (input) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_cardinfo_right .ginput_card_security_code {border: 1px solid red;}
example: card security code input (input) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_cardinfo_right .ginput_card_security_code {border: 1px solid red;}
example: card security code input (input) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .ginput_cardinfo_right .ginput_card_security_code {border: 1px solid red;}
Icon
example: card security code image (span) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_cardinfo_right .ginput_card_security_code_icon {border: 1px solid red;}
example: card security code image (span) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_creditcard .ginput_cardinfo_right .ginput_card_security_code_icon {border: 1px solid red;}
example: card security code image (span) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_creditcard .ginput_cardinfo_right .ginput_card_security_code_icon {border: 1px solid red;}

Creating a Feed for the HipChat Add-On

Creating a Feed for the HipChat Add-On

SummaryCreate a FeedFeed Settings Screen

The HipChat service was discontinued in 2019 after acquisition by Atlassian.The Gravity Forms add-on is no longer available for download. These documents have been left for posterity only, and will be removed in time.
Summary
Before the HipChat Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, a notification to a HipChat Chat Room when a form is submitted.
Create a Feed
To create a feed to HipChat using the HipChat Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with HipChat.
Once within your desired form, hover over Settings and click on HipChat.
Click Add New to create a new feed. You will be presented with the HipChat feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshot below.

A feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
Under HipChat Room, select the room you want the notification to go to.
Select the Notification Color that HipChat will use for the background of the notification to distinguish it from standard chat.
Select if you』d like to Send User Notification when the notification appears in HipChat. This will use HipChat』s built in audio/visual cues to alert users in the chatroom of the notification.
Configure the Message of the HipChat notification. This is what will appear in HipChat.
Conditional Logic: If unchecked, every successful form submission will be sent to HipChat. If you wish to set specific conditions for sending form data to HipChat, then check the 「Enable」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Date

Date

SummaryCommon SettingsGeneral SettingsMerge TagsUsageModifiers

Summary

The Date field allows you to present a field that captures date data using the jQuery UI date picker. It is available under the Advanced Fields section within the form editor.

Date field as displayed in the Field Library

Date field as displayed in the Form Editor.

Common Settings

This field uses only common field settings for the Appearance and Advanced settings. For a description of each of the common field settings, refer to this article. Below you will find description of specialty settings that are particular to this field.

General Settings

SettingDescriptionDate Input TypeDate Picker will let users select a date from a calendar.Date Field will let users free type the date.Date Drop Down will let users select date from drop downs.IconAllows you to set an icon which will be listed beside the date field. Options include: No Icon, Calendar Icon, Custom IconDate FormatSelect the format you would like to use for the date input. Available options are MM/DD/YYYY and DD/MM/YYYY.

Merge Tags

For more information on the use of merge tags, refer to these articles.

Usage

{Field Name:2:modifier}

Notes:

The field name is optional.The second parameter defines the ID of the field that will be output in this tag.Within the third parameter, you can define an optional modifier to use. Only one modifier can be used per merge tag.

Modifiers

ModifierDescription:yearOutputs only the year used in the field.:monthOutputs only the month used in the field.:dayOutputs only the day used in the field.:ymdOutputs the date formatted as year/month/day. Example: 2016/10/31.:dmyOutputs the date formatted as day/month/year. Example: 31/10/2016.

Creating a Feed for the Slack Add-On

Creating a Feed for the Slack Add-On

SummaryCreate a FeedFeed Settings ScreenSending MessagesTeam Invites (deprecated)Other Settings

Summary
Before the Slack Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, form data being sent to Slack.
Create a Feed
To create a feed to Slack using the Slack Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with Slack.
Once within your desired form, hover over Settings and click on Slack.
Click Add New to create a new feed. You will be presented with the Slack feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshots below.

A feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
For Action, chose either Send Message and Invite to Team. The feed can be configured to either send a message inside Slack or invite a user to a Slack team.

Sending Messages
When Send Message is chosen as the Action, the following settings will display:

Send To: Based on your selection here, you will be able to send the triggered message to a channel, group, or individual.
Slack Channel: Select the specific channel, group, or individual that the message should be sent to. Use this drop down to select your desired destination. If you want it to go to multiple selections, you can simply create additional feeds.
The Message setting determines the content of the message that will be sent by the feed. Within this box, enter any text you would like to be within the message. This text area also supports the use of merge tags to dynamically generate content.

Team Invites (deprecated)
This feature was deprecated with Slack』s adoption of their new API, the deprecation of their legacy API, and version 1.13 of our Add-On. Refer to this article for more information.
Team invites are only available if your Slack user is an administrator on the Slack channel associated with your key. If you are not an administrator, this option will not appear.
When Invite to Team is chosen as the Action, the following settings will display:

Use the Email Address dropdown to select the field that contains the email address the invite will be sent to.
First Name: Use the dropdown to select the field within your form that will be used for the corresponding value.
Last Name: Use the dropdown to select the field within your form that will be used for the corresponding value.
Slack Channels: Select the channel that the message should be sent to.
Slack User: Use this drop down to select the user that the message should be sent to.
The Message setting determines the content of the message that will be sent by the feed. Within this box, enter any text you would like to be within the message. This text area also supports the use of merge tags to dynamically generate content.

Other Settings

Image Attachments: Select which file upload fields will be attached to the Slack message. Only image files will be attached.
Conditional Logic: If unchecked, every successful form submission will be sent to Slack. If you wish to set specific conditions for sending form data to Slack, then check the 「Enable」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Create a Custom Field

Create a Custom Field

IntroductionExamples

Introduction
When using the Settings API you can define a custom field type by creating a function called settings_{your_custom_field_type}. The text after the first underscore will be what you decided to name your type. The function will run for every field of that type.

Important: The Settings API is not used to create custom form fields. To create custom form fields you would need to extend the GF_Field class, part of the Field Framework.

Examples
The following example renders the field for the field type my_custom_field_type. This function creates two text box fields.:
public function plugin_settings_fields() {
return
array(
array(
'title' => 'This is the title for Section 1',
'description' => 'This is a description of the purpose of Section 1',
'fields' => array(
array(
'label' => 'My Custom Field',
'type' => 'my_custom_field_type',
'name' => 'my_custom_field'
),
)
),
);
}

public function settings_my_custom_field_type(){
?>

My custom field contains a few settings:

settings_text(
array(
'label' => 'Item 1',
'name' => 'my_custom[1]',
'default_value' => 'Item 1'
)
);
$this->settings_text(
array(
'label' => 'Item 2',
'name' => 'my_custom[2]',
'default_value' => 'Item 2'
)
);
}

The following example has a custom field type named 「text_with_checkbox」. This custom type creates a text box field and a checkbox field.
public function plugin_settings_fields() {
return
array(
array(
'title' => 'Custom Types',
'fields' => array(
array(
'type' => 'text_with_checkbox',
'name' => 'text_checkbox',
'label' => 'Text box with a checkbox',
),
),
),
)
}

public function settings_text_with_checkbox(){
?>

This is a custom field type which will create a text box and a check box

settings_text(
array(
'label' => 'Text Box With Checkbox',
'name' => 'txt_cbx[1]',
'default_value' => 'Item 1'
)
);

$this->settings_checkbox(
array(
'label' => 'Checkbox',
'choices' => array(
array(
'label' => 'Checkbox',
'name' => 'txt_cbx[2]',
),
),
)
);
}