No commit activity in last 3 years
No release in over 3 years
Post iTunes Connect report data to your Slack channels.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.6
~> 0

Runtime

 Project Readme

Slack iTunes Connect Autoingestion

This gem will add a Slack incoming webhook endpoint for pulling iTunes Connect report data and posting it back to your Slack channel.

Installation

You can deploy a functioning app right to heroku:

Deploy

Or for a DIY setup, add this line to your application's Gemfile:

gem 'slack_itc_autoingestion'

And then run:

$ bundle install

Configuration

You'll need to setup two integrations in your Slack:

  1. An Incoming Webhook. The Webhook URL field will be used in your config below.
  2. A Slash Command. The Command and Token fields will be used in your config below. The URL field should be something to the effect of https://example.com/slack_itc_autoingestion.

By default, the config looks for options set in your environment variables. Override the defaults in config/initializers/slack_itc_autoingestion.rb:

SlackItcAutoingestion.configure do |config|
  config.itc_username = ENV['ITUNES_CONNECT_USERNAME']
  config.itc_password = ENV['ITUNES_CONNECT_PASSWORD']
  config.itc_vendor_id = ENV['ITUNES_CONNECT_VENDOR_ID']
  config.slack_token = ENV['SLACK_TOKEN']
  config.slack_webhook_url = ENV['SLACK_WEBHOOK_URL']
  config.slack_command = '/itc'
end

Usage

In any public Slack channel you can type: /itc [report_date] [date_type] [report_type]

report_date is date in the format YYYYMMDD. Defaults to 24 hours ago.

date_type is 'Daily' or 'Weekly'. Defaults to 'Daily'.

report_type is 'Summary' or 'Opt-In'. Defaults to 'Summary'.

Contributing

  1. Fork it ( https://github.com/[my-github-username]/slack_itc_autoingestion/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request