Send a message to a flowdock team inbox or chat using the push API (see https://www.flowdock.com/api/team-inbox and https://www.flowdock.com/api/chat)
parameter | required | default | choices | comments |
---|---|---|---|---|
external_user_name |
no | (chat only - required) Name of the "user" sending the message | ||
from_address |
no | (inbox only - required) Email address of the message sender | ||
from_name |
no | (inbox only) Name of the message sender | ||
link |
no | (inbox only) Link associated with the message. This will be used to link the message subject in Team Inbox. | ||
msg |
yes | Content of the message | ||
project |
no | (inbox only) Human readable identifier for more detailed message categorization | ||
reply_to |
no | (inbox only) Email address for replies | ||
source |
no | (inbox only - required) Human readable identifier of the application that uses the Flowdock API | ||
subject |
no | (inbox only - required) Subject line of the message | ||
tags |
no | tags of the message, separated by commas | ||
token |
yes | API token. | ||
type |
yes |
|
Whether to post to 'inbox' or 'chat' | |
validate_certs (added in 1.5.1) |
no | yes |
|
If no , SSL certificates will not be validated. This should only be used on personally controlled sites using self-signed certificates. |
- flowdock: type=inbox token=AAAAAA from_address=user@example.com source='my cool app' msg='test from ansible' subject='test subject' - flowdock: type=chat token=AAAAAA external_user_name=testuser msg='test from ansible' tags=tag1,tag2,tag3
For more information on what this means please read Extras Modules
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Helping Testing PRs and Developing Modules.