Webhooks are part of the Public API scope, and that project is well under way. We’re hoping to ship in June. We’ll keep you posted.
Wow. That is... amazing. Goldberg would be proud. :p
A quick update: these are almost ready, we're just getting our Slack integration out the door first, and then will move on to Webhooks. Thanks for your patience.
Hi! As you may have seen, we’re getting very close to a public API. But we need your help!
If having a Flow public API is important to you, please take a couple minutes to fill out this short survey and let us know what you’re looking for. It would be a big help:
And if you’d like to hop on the list for early beta access, head to app.getflow.com/preferences and look for the beta opt in. We’ll also send out an email to beta participants when beta access becomes available.
Hi Kevin, yeah. The first incarnation of this is being built as a set of outgoing webhooks. Those will be made publicly available after our release of the Slack integration. Thanks for checking in.
We’ve kicked off design for a feature that includes this functionality.
Hey Zachary, we've got a lot on the go, so while we do want to build this, it is competing for our attention. I should also note that our route to building this is blocked by some stuff that would really hamper Flow's performance, so it's turning out to be trickier than we would have hoped.
We don’t plan to make section selection easier in the task pane right now, but do want to work on it at some point.
Okay, got it. I'll edit your language in the suggestion. We don't plan to make section selection easier in the task pane right now, but do want to work on it at some point.
This is something we’ve talked about both as a team and the makers of this product. As it stands, with project notes at your disposal, you can mention the project owner in the note for the project. I’m wondering if there is anything more you’d want from a project owner? What would help them do their job better?
That's a good suggestion. Makes total sense. Thanks James!
Got it. Thanks for clarifying! We'll keep this idea in mind in the backlog.
Hi Becky, if your projects have so many moving pieces, it might make sense to move down a level in your planning. Make the pieces tasks (instead of sections) and their steps subtasks (instead of tasks) and you may have a much more manageable setup. This would also be much easier to duplicate.
We plan to address this some time this year. Prioritization is clearly important to teams and the way they work.
Hey Ben, we're still wanting to take prioritization further; kanban is just part of it.
No plans to add this yet. We’ll update if that changes, and continue to follow this idea.
Interested to hear how you're assigning due times for your tasks. Adding tags or renaming the name of the task to include the hour?
We plan to work on this. It might be helpful to talk to some of you about it, so we’ll be reaching out at some point in the next little while.
Hey Ben, not sure what you're looking for here. Want to add some clarification?
Internally, we use a template project for our launches which holds the predefined list of launch tasks and just duplicate it as needed.
Hi Delphine, thanks for your suggestions.
Could you clarify what you mean in #1?